Database Info

[Q] Error updating to 1.78.401.2

I tried to update my 1.53.401.2 to the latest OTA 1.78.401.2.
But with the normal Android OTA method, it gives me an error that it can't find the 7digital3.0.apk file. Of course it can't find it. I deleted it. But I didn't make a backup of it before deleting it
So I tried to copy the OTA zip to the "internal SD card", rename it to update.zip and flash it with CWM Recovery. This also doesn't work. It tells me, that I have a wrong CID (HTC__102).
Could anyone be so kind to upload the 7digital3.0.apk (and .odex) from the 1.53 rom?
Thanks!

Here you go mate, extract it and you will find the files you need...
If the OTA doesnt work, and flashing in recovery fails, open the .zip and modify the android-info.txt to match your CID..
if you dont know your CID, boot into fastboot and using adb type in ''fastboot getvar cid'' Without quotes

There should be an option to have the updater just skip whatever it can't find or which throws up inconsistencies with the DIFF updating...

psych0t1c said:
There should be an option to have the updater just skip whatever it can't find or which throws up inconsistencies with the DIFF updating...
Click to expand...
Click to collapse
I just did that now... Modifying the update script and skip updating the pre-installed apps that i deleted. ReZipped, signed, put on sd card, install from cwm recovery.
EDIT: Everything works except the SystemUi.apk... I had the 1% battery mod.
EDIT2: I reinstalled the correct SystemUI.apk by flashing the stock battery SystemUI.apk for 1.78, but since it crashed the first time, it won't start anymore at boot... Anyone knows how to fix that?

same problem, other apk...
romansvillage said:
I tried to update my 1.53.401.2 to the latest OTA 1.78.401.2.
But with the normal Android OTA method, it gives me an error that it can't find the 7digital3.0.apk file. Of course it can't find it. I deleted it. But I didn't make a backup of it before deleting it
So I tried to copy the OTA zip to the "internal SD card", rename it to update.zip and flash it with CWM Recovery. This also doesn't work. It tells me, that I have a wrong CID (HTC__102).
Could anyone be so kind to upload the 7digital3.0.apk (and .odex) from the 1.53 rom?
Thanks!
Click to expand...
Click to collapse
i have the same problem. but i deletet the system ap picasa_GLRplugin.apk. no backup before deleting... :-(
Could anyone be so kind to upload the picasa_GLRplugin.apk from the 1.53 rom?
thank you!!!

Unable to install update.zip

Im trying to update the modem from EP4D to FP1H using CWM, but when I start the installation, it gives me the error
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/668fc9f366e2.update_SCH-I510_EP4D_to_FP1H (1).zip
(Status 7)
Installation aborted
does anyone know how to fix this? I've tried re-downloading the update file, but nothing I've tried has worked.

Just thought of something. Do I need to convert back to the stock file system in CWM before I can install the update? I'm on EXT4 right now.

savan12986 said:
Im trying to update the modem from EP4D to FP1H using CWM, but when I start the installation, it gives me the error
file_getprop: failed to stat "/system/build.prop": No such file or directory
E:Error in /sdcard/668fc9f366e2.update_SCH-I510_EP4D_to_FP1H (1).zip
(Status 7)
Installation aborted
does anyone know how to fix this? I've tried re-downloading the update file, but nothing I've tried has worked.
Click to expand...
Click to collapse
You must rename the update file to just "update. Zip" but make sure you are stock ep4d before updating.
Sent from my SCH-I510 using xda premium

You can't be on anything custom when attempting to flash that package.

ok, thanks. I used your stock conversion pit file & rom Imnuts to get back, then I just took all the OTA updates to get to the FP1 modem

.30 Update Red Exclamation

I just got the OTA for the .30 firmware so I put back the stock build.props and the two client apk and odex files, but when trying to update I got an image of a fallen over android with a red exclamation.
What is wrong?
Sent from my ASUS Transformer Pad TF700T

Same for me

Isn't that the stock recovery screen?

see the install logs in /cache/recovery/ for details, there you should find a reason why it failed

the file size is 4.5kb. The text viewer shows an empty file.

usern ameisval idandnot said:
the file size is 4.5kb. The text viewer shows an empty file.
Click to expand...
Click to collapse
The actual file size of the .30 update is over 200 MB. I'm guessing file didn't download right.
My tablet wouldn't auto update .26 OR .30
Had to install from micro SD. Not sure why. I'm rooted, but still locked and running stock.

usern ameisval idandnot said:
the file size is 4.5kb. The text viewer shows an empty file.
Click to expand...
Click to collapse
Same, I can't open the logs either.

hshah said:
Same, I can't open the logs either.
Click to expand...
Click to collapse
I had the same and the reason was that I had a modified version of file build.prop (modified to have a different dpi value). And the OTA is checking wether or not you have a stock version of build.prop (and also of another file but don't remember which one) and if it founds that your tablet is not stock anymore at 100% then it will fail with the android/red triangle.
To resolve there are 2 ways :
- restore back the stock version of build.prop (and other file)
or
- do manual update (by downloading the .30 firmware from Asus support web site and putting on /sdcard and rebooting)
ps : that issue has already been discussed several times and you could find more detailed "how to" in other threads

Ghorin said:
I had the same and the reason was that I had a modified version of file build.prop (modified to have a different dpi value). And the OTA is checking wether or not you have a stock version of build.prop (and also of another file but don't remember which one) and if it founds that your tablet is not stock anymore at 100% then it will fail with the android/red triangle.
To resolve there are 2 ways :
- restore back the stock version of build.prop (and other file)
or
- do manual update (by downloading the .30 firmware from Asus support web site and putting on /sdcard and rebooting)
ps : that issue has already been discussed several times and you could find more detailed "how to" in other threads
Click to expand...
Click to collapse
PS. If you read my post, I have already restored the stock versions of the necessary files so this issue should not occur.

How to's didnt help because I have a 100% Original stock device.

If anyone still have trouble updating.
As d14b0ll0s said, use a root file browser and see bottom of the /cache/recovery/last_log file right after reset from failed update. If you have trouble opening up that file (empty) copy it to some folder on sdcard (Documents, etc.) and open that.
In my case, i forgot to rename CMClient back to .apk

I dunno if this will help but I have a stock 700. I wanted to reflash the 30 update as I was having problems with the OTA I got. I d/l from Asus the correct US version and unzipped it and copied the zip file I got from that to my root on the sdcard. All this was done on the PC. I got the same error as you all wheb I tried to perform the flash. Then I changed the name of that zip file to EP201_768_SDUPDAT.zip while it was on the PC and copied that to the sdcard again. Followed the alternative firmware update method (found here http://forum.xda-developers.com/showthread.php?t=1755576) and it worked. It helped as most of the weird crap has stopped happening and now I have the normal crap happening like everyone else.

My Solution was to kill the Pad. Now I updated to JB. Works perferctly.

.26 & .30 always did the same, and i had to manually update from SD card. NOW, same thing with JB. Voodoo has also never worked. I have a locked, rooted, stock device. I think I'm gonna take it back to best buy since i have protection plan.

Does anyone have a dump of their system folder? I deleted loads of apps which is stopping me upgrading to JB
Sent from my GT-I9300

My device complains about a file called Vibe_CN.apk.
Does anyone have this file on WW .30 firmware and is able to upload it somewhere?
I'm pretty sure I haven't fiddled with this file, but according to the log below, it doesn't match the expected hash...
Verifying current system...
file "/system/app/Vibe_CN.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/Vibe_CN.apk", "c36a7d96df630bfa6ab4e6a9484ac71f88d7c677", "297e177c2fd02d277792fe9b23b57c31ab67642c")
assert failed: apply_patch_check("/system/app/Vibe_CN.apk", "c36a7d96df630bfa6ab4e6a9484ac71f88d7c677", "297e177c2fd02d277792fe9b23b57c31ab67642c")
E:Error in /cache/dlpkgfile

Help needed!

i need help with modifying / creating the updater script in the meta-inf folder of a custom rom.
the reason for this is that, i just added ota updates to my rom, and everytime i push an update to my device (test), it gives me the following error when installing in cwm:
E:/ failed to load keys
/res/keys No such file or directory.
thats happens when the app tries to do it automatically. then i try it manually by toggling the signature verification in cwm.
and my guess was pretty much that it had something to do with the updater script.
so guys, please help me out and fast!
thankyou!

Can't restore TWRP backup E:Unable to find file system (first period)

Device: Xiaomi Mi Max 2 running MIUI 9, TWRP v3.1.1-0.
I was running MIUI 9 global developer ROM, but then I wanted to try the Lineage OS ROM. So I went into TWRP, made a backup (checked all boxes) and transfered the file to my PC. Then when I wanted to go back to MIUI, I transfered the file back, but when I try to restore it I get the folowwing error codes:
E:Unable to find file system (first period).
E:Unknown restore method for '/efs2'
It doesn't matter if i restore a MIUI ROM backup or Lienage OS backup, error still occures. I have done this plenty of times on other phones so I wonder what the problem is.
Here is the full log started with the backup:
[RESTORE STARTED]
Restore folder: '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS'
Skipping Digest check based on user setting.
Calculating restore details...
I:InfoManager file '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efs1.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efs2.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efs2.info' not found.
E:Unable to find file system (first period).
I:Single archive
I:InfoManager file '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efsg.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efsc.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager loading from '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/firmware.info'.
I:Read info file, restore size is 76745728
I:InfoManager file '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/dsp.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager loading from '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/persist.info'.
I:Read info file, restore size is 450048
I:InfoManager file '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/recovery.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager loading from '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/system.info'.
I:Read info file, restore size is 1114588672
Restoring 5 partitions...
Total restore size is 1256MB
I:Restore filename is: /data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efs1.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring EFS...
I:Reading '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efs1.emmc.win', writing '/dev/block/mmcblk0p41'
I:Restore filename is: /data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efs2.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring efs2...
I:Reading '/data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/efs2.emmc.win', writing '/dev/block/mmcblk0p42'
I:Restore filename is: /data/media/0/TWRP/BACKUPS/a2d1d82d/lineageOS/
E:Unable to find file system (first period).
E:Unknown restore method for '/efs2'
Any help is appreciated!

I think you want to change your android version backed up lineage os. First flash fresh clean lineage os.. then restore backed up data
Sent from my SHV-E210S using Tapatalk

[email protected] said:
I think you want to change your android version backed up lineage os. First flash fresh clean lineage os.. then restore backed up data
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
Thanks for your answer, unfortunately I already tried that to no avail. I also tried flashing the same ROM as the backup and only check "data" because it doesn't fail there. But then it won't boot and is stuck on the bootscreen.

FrikandelKonijn said:
Thanks for your answer, unfortunately I already tried that to no avail. I also tried flashing the same ROM as the backup and only check "data" because it doesn't fail there. But then it won't boot and is stuck on the bootscreen.
Click to expand...
Click to collapse
First make a way to boot your phone. So Intall stock rom through odin. Then install lineage os again and restore your data
Sent from my SHV-E210S using Tapatalk

[email protected] said:
First make a way to boot your phone. So Intall stock rom through odin. Then install lineage os again and restore your data
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
Isn't Odin only for Samsung phones?
Also, not sure if I worded it right one post before this, but I wiped the whole phone, then isntalled Lineago OS and then restore de DATA partition from the backup.

FrikandelKonijn said:
Isn't Odin only for Samsung phones?
Also, not sure if I worded it right one post before this, but I wiped the whole phone, then isntalled Lineago OS and then restore de DATA partition from the backup.
Click to expand...
Click to collapse
Ohh...sorry...I forgot your phone model...however install stock rom again
Sent from my SHV-E210S using Tapatalk

[email protected] said:
Ohh...sorry...I forgot your phone model...however install stock rom again
Sent from my SHV-E210S using Tapatalk
Click to expand...
Click to collapse
Yeah I already did that, doesn't work. I've found another way though to make bakups, I just use Titanium backup. Atleast with that backup tool I can restore app + app data on other ROM's.
If other people have a similair problem, and they do want to get the backup back, they can try this: https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/.
Note that I didn't try that and I'm not certain it will work!

FrikandelKonijn said:
Yeah I already did that, doesn't work. I've found another way though to make bakups, I just use Titanium backup. Atleast with that backup tool I can restore app + app data on other ROM's.
If other people have a similair problem, and they do want to get the backup back, they can try this: https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/.
Note that I didn't try that and I'm not certain it will work!
Click to expand...
Click to collapse
I had the same problem with restoring my TWRP backups on SM-G860P. I attempted the method you suggested here https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/
How to Fix EFS from TWRP recovery
Boot into TWRP recovery.
From TWRP’s main screen, select Advanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot device.​
Now I'm unable to make and receive calls. Is there a way to reverse this? Thanks