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?
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.
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
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.
[SOLVED] - Apparently, I lost the ability to *read* also. When I went into TWRP, I must have clicked the "keep the system read-only" button. That would prevent me from deleting files/folders. I hereby select one card from the Smacktard pile.
Evening all,
Sprint Note 5, Rooted.
Tried to manually make an application a "System App". This is what happens when you give a monkey the *tools* but not the *brains*. I'm plenty technical, but I've not done this before.
I installed an app, then went into the data\apps directory and copied the entire application's folder into \system\app.
When I rebooted, the phone gets stuck on the Sprint LTE screen.
When I boot into TWRP, and into Advanced / File Manager, then go into the offending directory, I get the following:
File Operation Complete
Failed
rm -rf "/system/app/com.incorporateapps.fakegps.fre-1" processes ended with ERROR: 1I get similar messages when I chmod, delete, move, or rename.
Any assistance you could provide would be MUCH appreciated. I'm bricked and cannot work until I get my phone back.
Thanks!
Pete
have you tried to flash stock rom or another rom ?
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Have you check that you have downloaded and installed the correct version of the OS on your device?
pazler said:
i have a note 8 sm n950 i done the android update a few months ago and and it got my phone stuck in a boot loop, i installed new firmware which i was able to use the phone again but lost data signal, i fixed that but now my calls and text are coming through with a german number (im in the UK) i have tried to install stock firmware using odin and keep getting sw rev check fail device 11 binary 6 (and other variations of that error) i have also tried clearing the cache and wiping the phone from the boot menu but no luck, could anyone help, i would be very grateful
Click to expand...
Click to collapse
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
stonedpsycho said:
The binary error you are getting is because you are trying to flash older filmware than what is already on the phone., this is not possible because of security updates. Downloading the latest filmware for you device should resolve this error, and then hopefully fix the other errors you face.
Click to expand...
Click to collapse
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
pazler said:
im pretty sure i have tried the latest one for my phone, as i have tried many others but i was never 100% certain it was, could you point me in the direction of one?
Click to expand...
Click to collapse
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
stonedpsycho said:
In post number 2 in the thread below, you can install "samfirm" on your Pc, this will give you the latest update to download, at a fast speed. For region (on samfirm) put your service provider, ie BTU or XEU for the UK.
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
Click to expand...
Click to collapse
seems to of worked fine, no problems yet, thank you!
pazler said:
seems to of worked fine, no problems yet, thank you!
Click to expand...
Click to collapse
Glad to hear :highfive:
stonedpsycho said:
Glad to hear :highfive:
Click to expand...
Click to collapse
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
pazler said:
sooooo.... it was working fine for a couple days then the phone froze with a glitched horizontal line on the screen, i rebooted the phone and thought nothing more of it. A day later did the same thing (different place in the screen this time) i have wiped the cache a few time times but it hasnt improved. It is also freezing on the samsung loading screen and or getting stuck in a boot loop, the phone does work normaly for short amounts of time (few hours or so) but keeps happening, i managed to copy this log from the recovery menu if any help
p.s this is simlar to the original problem i was having before i changed the firmware
fail to open recovery_cause(no such file or directory)#
#reboot recovery cause is [unknown]#
support single-sku
file-based OTA
supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# manual mode v1.0.0#
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT'(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/cid/sysconfig'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
can't open directory '/sytem/omc/SUP/ect/permissioins'.(No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : no such file or directory
Click to expand...
Click to collapse
This is beyond my knowledge. I would take a guess that you have some sort of hardware issue as flashing stock filmware usually resolves any software bug. Hopefully someone who has faced the same or someone more knowledgeable will be able to help you further.
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
mehroz1234 said:
HI Experts i am getting the same issue in my note 8 sm-n950f according to my knowledge i lost its efs and baseband partition by mistake and my phone now stuck on Galaxy Logo now the OEM System is locked by default i am not able to flash TWRP please Suggest me how can i recover pretty phone back in Normal Condition :crying:
Click to expand...
Click to collapse
As we have said many of times before, if you lost your EFS folder and you never made a backup of it then you're screwed and you'll need to send it to Samsung for repair because you can't use anyone else's EFS because the EFS holds your IMEI and the phones serial numbers and such. It's information that's never supposed to be removed or deleted.. However someone else said if you delete certain stuff in the EFS folder and then reflash it that it would work and I tried this method and it failed to work so I don't know any other way except sending it to Samsung repair facility.. It also requires root access which you obviously can't do since it's OEM is not unlocked so I really doubt there's anything you can do short of sending it to Samsung..
https://forum.xda-developers.com/ga...i-detect-sim-card-t4134733/page2#post83127549
This is the link but like I said this didn't work for me..