Hi all,
I finally got offered the JB OTA update but it fails to apply because I used TimeZone Fixer to update my timezone files. From the recovery log (/cache/recovery/last_log):
Code:
Verifying current system...
file "/system/usr/share/zoneinfo/zoneinfo.dat" 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/usr/share/zoneinfo/zoneinfo.dat", "6d285c458b0a42ae5310f8695ef84931a92cf8db", "413b1e0fdd323e9fdba5111132122bd311651a32")
assert failed: apply_patch_check("/system/usr/share/zoneinfo/zoneinfo.dat", "6d285c458b0a42ae5310f8695ef84931a92cf8db", "413b1e0fdd323e9fdba5111132122bd311651a32")
I thought I'd just restore these files from the 4.0.4 image I'm running now but while I have a large system.img.ext4 I can't figure out how to get anything out of it. It does not mount as an ext4 partition...
Does anyone know how I can extract the original timezone files for this phone?
Or can anyone send me the set of timezone files from this phone?
Or is there some other way to get the JB update installed (without resorting to a full phone wipe)?
I do have a backup of the phone's contents on an external SD card but I'd prefer not to wipe if possible.
Thanks in advance...
a1291762 said:
Or is there some other way to get the JB update installed (without resorting to a full phone wipe)?
Click to expand...
Click to collapse
Because I'm impatient and because I was bored, I looked at the fastboot image I had. It seems the "wipe" bit is optional so I flashed up the system part, leaving the rest intact. That left me with a cleaned out /system but didn't do anything to my apps (well... doesn't seem to have done anything to them - I haven't checked yet). Then I did the OTA process. Did you know you can put an OTA zip under /cache to avoid having to re-download it? The software says it's going to re-download but I guess it does an rsync or something so it completes quickly. Nice.
So... I'm now in the process of installing JB! It's been running longer than it did last time so here's hoping...
update: it's all going now.
Sent from my XT890 using xda app-developers app
Related
For those of you using Safestrap and want to restore your "preinstall" back to stock but don't have a backup to restore from:
Download the below file and unzip it under your "safestrap/backup" directory on the SD card.
Inside Safestrap you can do an "Advanced Restore" and select "System" and then choose this backup.
Download: http://www.mediafire.com/?3zfz332vefe84j3
MD5SUM: 1e13bd36d5f04b7d0f03e11fa28e36d8
So flashing this would return your device to stock out of box condition or is this just for your "safe" system in safestrap?
debating whether to try your ICS rom but wanting to be sure I can get back to factory conditions if I absolutely must, just moved from hd2 running android so bootloader stuff is different.
Whenever I try restoring this backup it always comes up saying md5 mismatch... not sure what to do in that case.
Sent from my DROID4 using XDA
Coriolis3ffect said:
Whenever I try restoring this backup it always comes up saying md5 mismatch... not sure what to do in that case.
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Try deleting the file, clearing your browser cache, and then redownloading.
Sent from my DROID4 using XDA
Didn't work, so I'm just going to stick with the stock rom in safe mode and leave it at that
nm wrong thread
is it me or does this back up only contain 3 files, one of them being Let's Golf game? i opened the backup file in WinRar and that's all I see.
The original link is dead, and I need this now to install the ICS update. Anyone got it handy? Otherwise I'm going to have to see if I can pull it out of the full rom image.
[edit] never mind, got it from the full rom image.
highlandsun said:
The original link is dead, and I need this now to install the ICS update. Anyone got it handy? Otherwise I'm going to have to see if I can pull it out of the full rom image.
[edit] never mind, got it from the full rom image.
Click to expand...
Click to collapse
I have the full rom Image but how do I get it back?
Assume that is what i need to do.
I have an error:
qe 1/1
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Deleting Facebook cache folder...
Verifying Current System...
assert failed: apply_patch_check("/preinstall/Knowyourdevice/Motorola_XT894_Batterysave.3gp", "71ce34b3b53ae3a2d9bbfb9ce3ba4452d73ea98", "4e7e24a6817763a5539e569c9d7e15c6e430a27b")
E:Error in /cache/Blur_version.6.13.219.XT894.Verizon.en.US.zip
(status 7)
Installation Aborted
From the full ROM zip file, extract "preinstall.img" and copy it to the phone. I would use adb push to do it.
Code:
adb push preinstall.img /sdcard-ext/
adb shell
su
umount /preinstall
dd if=/sdcard-ext/preinstall.img of=/dev/block/preinstall bs=1024k
mount -t ext3 /dev/block/preinstall /preinstall
Then copy the ICS update files back to /cache and go to Settings / About Phone / System Updates again. It will check for the update, try to download it again, and then see that it's already downloaded. Then you can install it.
By the way, if there's anything on your /preinstall partition that you wanted to save, you must back it up before doing any of this.
When I got my Verizon P1800 7" Galaxy Tab last year, I rooted it and dumped a bunch of bloatware. Unfortunately, that is apparently what's been preventing the EC02 update from completing:
failed to stat "/system/app/DailyBriefing.apk": No such file or directory
file "/system/app/DailyBriefing.apk" 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/app/DailyBriefing.apk", "4bfd497e05908bbf7515a34010dc9f8657be51eb", "7876b4a8cc01030981d20e4a1e8f6a4bb82791a4")
I:try_update_binary -> ui_print(assert failed: apply_patch_check("/system/app/DailyBriefing.apk", "4bfd497e05908bbf7515a34010dc9f8657be51eb", "7876b4a8cc01030981d20e4a1e8f6a4bb82791a4"))
Click to expand...
Click to collapse
I found a copy of DailyBriefing.apk and pushed it into /system/app/ (it wouldn't install by itself). However I was unable to locate the matching DailyBriefing.odex.
Questions:
1. Does this matter? Will the mere presence of DailyBriefing.apk in the apps/ directory make the update script happy? Or do I also need the odex file? DailyBriefing shows an icon but FC's if you try to open it.
2. Is there a way to force the EC02 update to run again without waiting a week for the Tab to notice it needs it? If I click Settings -> About Device -> System Updates it says "Your system is currently up to date", even though it isn't. I'm still on DJ11, kernel 2.6.32.9 with [email protected] #3.
3. Is there a way to edit the update script to just tell it to forget about DailyBriefing?
I've been up and down the FAQ's and a ton of other threads here and on other boards without finding anything about this. Thanks!
Someone? No one? Anyone?
Background: I've been using CM9 for quite a while; finally decided to install the ICS leak underneath to try to improve the radio issues. I switched Safestrap back to the unsafe boot (stock), then went through the ICS leak instructions; flashed the 6.13.219 fastboot images using Windows RSDLite (Linux wouldn't flash the webtop image via fastboot command-line ), booted up, rooted it, installed and configured OTA Rootkeeper, then tried to install from stock recovery. I'm getting this, though:
Code:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature length doesn't match EOCD marker
E:signature verification failed
Installation aborted.
One caveat is that I did softbrick it because the battery died while RSDLite was working on that webtop image (amazing how fast the battery drains at the bootloader). I was able to resolve that, though.
Has anybody else had this problem; if so, how were you able to fix it? I haven't been able to find any other similar reports via Google.
Any help greatly appreciated. I love CM9, even with the radio issues, but it would be nice to reduce the severity
Based on the error description it sounds like there something wrong with the update zip you are trying to flash. I would try redownloading the update and see if that works.
Sent from my Droid 4
kwyrt said:
Based on the error description it sounds like there something wrong with the update zip you are trying to flash. I would try redownloading the update and see if that works.
Sent from my Droid 4
Click to expand...
Click to collapse
I've tried I also tried using the .213 build instead of .215; same problem. Do you know what hash algorithm is used for the .crc file? It looks like a CRC32 in decimal, and if that's the case, both of my Blur_Version.6.13.219.XT894.Verizon.en.US.zip files are corrupted - but I'm only guessing as to the algorithm.
Floppie7th said:
I've tried I also tried using the .213 build instead of .215; same problem. Do you know what hash algorithm is used for the .crc file? It looks like a CRC32 in decimal, and if that's the case, both of my Blur_Version.6.13.219.XT894.Verizon.en.US.zip files are corrupted - but I'm only guessing as to the algorithm.
Click to expand...
Click to collapse
I don't know what any of that means. LOL! But, if you are flashing the leak via stock recovery from your ext sd card you shouldn't even need the crc file.
Sent from my Droid 4
Yeah - I wasn't using it for the flash, I just wanted to use it to verify that my download wasn't corruped. A re-download yielded the same md5sum though.
reflash the Gingerbread .219 and this time don't root. Install the ICS leak and then root.
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
StATicxTW0T said:
So after some messing around today with one of the cm12 builds, everytime I try to do anything in twrp I get the error "E: Unable to stat ' /data/power_supply_logger/power_supply_info.bin' " and i have no idea how to solve it. The only effect it seems to have is it makes restoring and backing up data fail at the last second (although as far as I can tell all of the data makes it). The error is always right after "updating partition details". I've tried reflashing 2 or three different versions of twrp (2.7.1.1, 2.6.3.1, and 2.8.1) as well as restoring stock vzw firmware through rsd lite as well as the gpe rom to no avail. Any help would be greatly appreciated.
Also, when flashing cm12, i get "mount: failed to mount /dev/block/platform/msm_sdcc. 1/by-name/userdata at /data: Device or resource busy"
Click to expand...
Click to collapse
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
BinBug said:
I have the same problem with my moto g falcon XT1032.
Wen I try to flash CM 12 he gives the same error.
Click to expand...
Click to collapse
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
The first error or the second error
StATicxTW0T said:
The first error or the second? I've narrowed the first down to a missing file in my data folder. Unfortunately rsd'ing doesn't help. If anyone'd be willing to upload it for me that'd be awesome. It's the bin file in /data/power_supply_logger/
Click to expand...
Click to collapse
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
BinBug said:
Wen I try to flash te ROM he give me this:
Code:
Installing 'data/media/0/sideload.zip" ...
Checking for MD5 file ...
Skipping MD3 check : no MD5 file found
mont: failed to mount /dev/block/platform.msm_sdcc.1/by-name/userdata at /data: devices or resource busy
unmount of /data failed (-1): Devices or resource busy
E: Error Exexuting updater binary in zip ' /data/media/0/sideload.zip"
You say that i most change the bin file in /data/power_supply_logger/, but how?
link to rom that i use : CM12 for flacon
Click to expand...
Click to collapse
That error is caused by the version of TWRP you are using. Something about different versions and different updater scripts. Some have had sucess with 2.8.1, some with 2.6.3.1 and some with 2.7.1.1. You will need to try all three until you find the one that works for you. Do not touch the power supply file, that's whats causing my first error. Somehow it got deleted, and restoring to complete stock does not replace it, thats why i need someone to upload theirs.
I have an H811 with an unlocked boot loader and rooted with BETA-SuperSU-v2.67-20160121175247.zip. I do not have TWRP installed, but instead opt for fastboot boot trwp-xxx.img when I want to make a nandroid backup. I did not install TWRP specifically so I could use the OTAs when they come in from Tmo. The other day, one came in but the install fails. This is the error message. I'm not sure why GoogleTTS.odex and Hangouts.odex are missing.. I may have froze them in Titanium Backup or accidentally removed them during a bloat cleansing., but it doesn't seem to be barfing on those two Google packages.. just the boot partition. Why?
I've not installed any mod kernels. Only thing I can think of is the unlocked bootloader. I have a stock nandroid that I can restore to the phone, and then possibly apply the patch, but if this is due to the unlocked bootloader that won't matter.
Second question: I have a saved copy of the update.zip from Tmo. I've read that trying to install this from TWRP is a bad idea. Is there another way to kick off the install instead of waiting for the download from Tmo again every night?
Thanks
HTML:
Verifying current system...
failed to stat "system/app/GoogleTTS/oat/arm/GoogleTTS.odex": No such file or directory
failed to stat "system/app/Hangouts/oat/arm64/Hangouts.odex": No such file or directory
contents of partition "/dev/block/bootdevice/by-name/boot" didn't match EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391
file "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" 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: "EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
"EMMC:/dev/block/bootdevice/by-name/boot:28227584:bba9b35edd32cf7e117d238d9220ebfedb0b8155:28207104:f3a1ce0f44594bc48e57a0402d2044508ba3d391" has unexpected contents.
E:Error in /cache/update.zip
(Status 7)
[LGE][Recovery] Installation aborted. no valid image in CACHE.
I:Saving locale "en_US"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_US"
[email protected]:/cache/recovery #
Nevermind. After some more searching, this is a really common problem with rooting and OTA. Sorry for the static. I'm new to all this.