Hey, I've been working on rooting my continuum with the new froyo leak. Everything seems to be working just fine and then when I try to run cwm recovery it always has the following message: E:failed to open/sdcard/update.zip (No such file or directory) E: signature verification failed Installation aborted.
I've tried starting over, renaming the zip file, deleting it from the sd card and putting it back on again, nothing seems to work and I continue getting the same message. PLEASE HELP!
choltzem said:
Hey, I've been working on rooting my continuum with the new froyo leak. Everything seems to be working just fine and then when I try to run cwm recovery it always has the following message: E:failed to open/sdcard/update.zip (No such file or directory) E: signature verification failed Installation aborted.
I've tried starting over, renaming the zip file, deleting it from the sd card and putting it back on again, nothing seems to work and I continue getting the same message. PLEASE HELP!
Click to expand...
Click to collapse
Use "toggle signature verification" in CWM ?
Forever living in my Galaxy Ace using XDA App
I don't have CWM. That is what I'm trying to reboot into when the file keeps saying it doesn't exist.
I followed all of the directions exactly, but perhaps there is something that I should have done or had on my phone before attempting?
I am about to give up trying to flash CM7 so here is my problem
When i select install from zip and choose the zip file, I get this message
-- Installing /sdcard/cm_galaxysmtd_full-181.zip
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Now I am running Darky Rom 10.2.2 with Crysis Sensation theme and the funny thing is I am able to i am able to flash the10.2.2 zip file and the Sensation theme but nothing else..
I even was able to flash MIUI which I was using for a few days before I eventually got this same error when i went to reflash it
Anyone here have a solution to this problem because I am starting to give up
Any help would be much appreciated
Disable signature verification, and see if that works. Most likely a problem with your ROM, SD Card, or some magical obstruction making the phone not read the SD Card properly.
GazaIan said:
Disable signature verification, and see if that works. Most likely a problem with your ROM, SD Card, or some magical obstruction making the phone not read the SD Card properly.
Click to expand...
Click to collapse
I disabled signature verification but still did not work...I can say it is probably a problem with my rom or sd card yet its odd that I can flash Darky Rom to 10.2.2, the key layout and a theme but nothing else...I am so confused lol
I flashed CWM recovery via Rom Manager which I read that I shouldn't of done...But I heard that I can flash back to stock then reroot my device...Any thruth to this? I just want to flash Cyanogen mod to my device, is that too much to ask lol
It's not a zip within a zip is it?
DirkGently said:
It's not a zip within a zip is it?
Click to expand...
Click to collapse
No it isn't
I know it has something to do with flashing CWM via Rom Manager because I wasn't able to flash any roms after I did that
here is the file to the new update. If anyone can make an update.zip out of it, it would be greatly appreciated.
https://www.dropbox.com/s/zkl4rqu4dyc3p8p/dlpkgfile
DroidEris1981 said:
here is the file to the new update. If anyone can make an update.zip out of it, it would be greatly appreciated.
https://www.dropbox.com/s/zkl4rqu4dyc3p8p/dlpkgfile
Click to expand...
Click to collapse
I suggest that you rename it to the file name that recovery will accept and it should flash as normally done with the full firmware (in theory).
Is this for us version?
did you adb pull off the cache?
thanks!
FYI - after renaming this to "US_epad-user-9.4.5.26.zip" and putting it in on the root of my MicroSD. The system detects the update right away, but also fails right away (android guy on his side - red exclamation). After I boot back into .22, I have a message waiting saying the the update failed becuase the update file was older the the current version (which simlply isn't true - I'm on .22 for sure).
The OTA file looks fine to me (manifest inside says it's .26)...
Anyone have any ideas?
EDIT: Here is the update portion of the error log from /cache/recovery (it simply believe's it's the wrong version!):
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /data/media/US_epad-user-9.4.5.26.zip
Opening update package...
I:1 key(s) loaded from /res/keys
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
E:check version fail
Installation version error.
I:result_code: 80000013
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.
Thanks!
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Redefined301 said:
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Click to expand...
Click to collapse
Trying this right now.
E:check version fail
Click to expand...
Click to collapse
clearly this is for .22 only US firmware.
Do you meet this requirement ?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Anyone else able to pull this patch file off cache for another region ?
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
eoh7678 said:
Trying this right now.
Click to expand...
Click to collapse
Do let us know if it works or not!
Redefined301 said:
All right this patch is for US firmware updating from
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615
to
asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.26-20120720
And try rename this file to "EP201_768_SDUPDATE.zip" and put it in the microsd, enter the recovery kernel and it should flash in theory(?)
Click to expand...
Click to collapse
OK, tried this and got the following:
Code:
Finding update package...
Opening bundle update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installing update...
Finding update package...
Opening update package...
E:Cannot find rule
SD Installation aborted.
Also, FYI, I got the OTA update notification and tried running it- it failed because I forgot that I had deleted some things from system/app that I never use (ie. ChromeBookmarkSyncAdapter, GoogleGarbageCrap, etc)
After reflashing the original .22 to replace, OTA insists that there is no update available. Any ideas for a fix there?
Redefined301 said:
clearly this is for .22 only US firmware.
Do you meet this requirement ?
---------- Post added at 02:43 AM ---------- Previous post was at 02:41 AM ----------
Anyone else able to pull this patch file off cache for another region ?
---------- Post added at 02:46 AM ---------- Previous post was at 02:43 AM ----------
Do let us know if it works or not!
Click to expand...
Click to collapse
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
eoh7678 said:
OK, tried this and got the following:
Code:
Finding update package...
Opening bundle update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installing update...
Finding update package...
Opening update package...
E:Cannot find rule
SD Installation aborted.
Click to expand...
Click to collapse
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Redefined301 said:
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Click to expand...
Click to collapse
Have already tried that- correct firmware installed, dlpkgfile for correct region placed in /cache, still no love.
Also, FYI, I got the OTA update notification and tried running it- it failed because I forgot that I had deleted some things from system/app that I never use (ie. ChromeBookmarkSyncAdapter, GoogleGarbageCrap, etc)
After reflashing the original .22 to replace missing and altered apk's and build.prop, OTA insists that there is no update available. Any ideas for a fix there?
Redefined301 said:
Well if you really want to update, you'll need to meet few requirements.
1. Have firmware "US_epad-9.4.5.22-20120615" installed at present.
2. Need to be "root" and put that file back into /cache.
Hopefully it should update?...
Click to expand...
Click to collapse
What should the filename be when putting it in the /cache folder? I haven't gotten that method to see the update yet...
Although, if it does the same "version check", then it'll probably fail as well.
I wonder if the folks that can't update are using a certain model dock or no dock at all? Actaully, I tried to update without the dock too - same issues. I have the dock with the TF700 model number...
jtrosky said:
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
Click to expand...
Click to collapse
Well. They pull the patch offline simply because they pulled it offline.
And supposedly if you don't see a firmware at the official support site then it's not officially released yet.
So, only a margin number of devices got updated OTA.
What does this mean?
Maybe they haven't finished with the firmware yet ..?
---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------
jtrosky said:
Correct - I am currently on US .22 (no question about that).
I also tried the other name EP01_768_SDUPDATE.ZIP - same issues an other poster (No rule error),
Could there be an additional file or two that we need from the OTA update??
Very strange (and frustrating)! Not sure why Asus doens't post the full ROM's on thier website right away... Would make this a lot easier!!
Click to expand...
Click to collapse
Simply put you can't have any of your existing files under /system or any other partition in the firmware except /data modified.
For the patch to work.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
jtrosky said:
What should the filename be when putting it in the /cache folder? I haven't gotten that method to see the update yet...
Although, if it does the same "version check", then it'll probably fail as well.
I wonder if the folks that can't update are using a certain model dock or no dock at all? Actaully, I tried to update without the dock too - same issues. I have the dock with the TF700 model number...
Click to expand...
Click to collapse
The same file name as it was originally came from.
Redefined301 said:
Well. They pull the patch offline simply because they pulled it offline.
And supposedly if you don't see a firmware at the official support site then it's not officially released yet.
So, only a margin number of devices got updated OTA.
What does this mean?
Maybe they haven't finished with the firmware yet ..?
---------- Post added at 02:57 AM ---------- Previous post was at 02:54 AM ----------
Simply put you can't have any of your existing files under /system or any other partition in the firmware except /data modified.
For the patch to work.
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
The same file name as it was originally came from.
Click to expand...
Click to collapse
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
jtrosky said:
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
Click to expand...
Click to collapse
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
jtrosky said:
Well, not sure what to say - I've even tried starting from a fresh .22 install - still no go. What's REALLY strange is that my tablet *did* see the update automatically this morning, but that original update failed just like it does when I try to do it manually now. Alsomost like once it fails, there is no way to update! Maybe a bug on Asus side?
Click to expand...
Click to collapse
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
eoh7678 said:
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
Click to expand...
Click to collapse
Ha! I'm trying that entire, exact same process one more time too! I'll report my findings as well.
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
Redefined301 said:
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
Click to expand...
Click to collapse
Yes, but doesn't a fresh install of .22 overwrite /system completely? Plus after that I'm doing a restore to factory defaults - so EVERYTHING should be back to stock...
eoh7678 said:
Same thing here, exactly. After failing the original OTA, it's as though the update stopped existing for my tablet.
I'm trying a full factory reset now- data/cache wipe, reloading .22, etc. Will update.
Click to expand...
Click to collapse
Did you messed with your /system too? If not then version should be correct ?
Redefined301 said:
I think it still fails for you is because you've messed with the /system too much or else where, then the patch file won't match cause it is looking for the correct files to patch.
And I wouldn't know what else you have done to your tablet so, best to wait for the next update.
Click to expand...
Click to collapse
I've just done a complete factory wipe- format /data and /cache, flashed the original US .22 firmware, and still says no OTA is available.
I'm going to try flashing to WW image and see what happens.
jtrosky said:
Ha! I'm trying that entire, exact same process one more time too! I'll report my findings as well.
---------- Post added at 03:13 PM ---------- Previous post was at 03:12 PM ----------
Yes, but doesn't a fresh install of .22 overwrite /system completely? Plus after that I'm doing a restore to factory defaults - so EVERYTHING should be back to stock...
Click to expand...
Click to collapse
Correct then that's for you to find out.
Since the OTA isn't available anymore so there's no point in trying to find out why and how it have gone wrong, does it?
Here my tablet updated earlier yesterday morning it's the TW version.
I'm not really sure what's changed in the kernel but it doesn't feel more responsive too, so guess the update isn't good enough... IMO.
---------- Post added at 03:20 AM ---------- Previous post was at 03:18 AM ----------
eoh7678 said:
I've just done a complete factory wipe- format /data and /cache, flashed the original US .22 firmware, and still says no OTA is available.
I'm going to try flashing to WW image and see what happens.
Click to expand...
Click to collapse
Don't bother because here I've got another tablet and it's not up to date yet checked for update and there's none available, the update was just available ota for few hours.
So let's put it this way, this is a BETA version and not supported.
Redefined301 said:
Correct then that's for you to find out.
Since the OTA isn't available anymore so there's no point in trying to find out why and how it have gone wrong, does it?
Here my tablet updated earlier yesterday morning it's the TW version.
I'm not really sure what's changed in the kernel but it doesn't feel more responsive too, so guess the update isn't good enough... IMO.
Click to expand...
Click to collapse
I'm not following. As far as I know, people are still receiving the update - it's not "pulled" or anything - just not working for a select few as far as I can tell.. I've also heard a lot of users saying that it makes a noticeble performance difference.
I give up - I guess we'll just have to wait for Asus to post the full version (it seems to take a week or so before they post the full firmware)...
Hello,
Thanks for taking the time out to read this!
I've been trying to get the manual Jellybean update to my Transformer Pad TF300T, US 9.4.3.30, rooted through Debugfs method, stock ROM.
Initially when I got the OTA notification, the update failed for a number of reasons - frozen apps, etc.
On removing the problems one by one, and after reading a lot of threads here at XDA, retrying the dlpkgfile method (as described at http://forum.xda-developers.com/showthread.php?t=1845377) with OTA root keeper and Supersu - factory reset and wiped dalvik cache; I am now stuck at this one issue with the Netflix.apk in /system/app/
Pasting the last_log contents from /cache/recovery/
Installing update...
Check : blob size = 13104069
Verifying current system...
file "/system/app/Netflix.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/Netflix.apk", "acbc5d5b8fce0a46ec74746e1ee8435630daa005", "459b736ea95188dd3500005f621b4fa22291c40c")
assert failed: apply_patch_check("/system/app/Netflix.apk", "acbc5d5b8fce0a46ec74746e1ee8435630daa005", "459b736ea95188dd3500005f621b4fa22291c40c")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I did try to reset device to factory settings three times, but update fails at the same point always. I couldn't find anyone else in the forum with a Netflix.apk issue, hence the post. I do not wish to unlock the bootloader if I don't have to. Could anyone help me with this please? Perhaps an upload of stock Netflix.apk that came with US 9.4.3.30?
Thank you very much!
I got all the original system apps for. 30 if you want the netflix one only pm me
Sent from the batman
joeyman08 said:
I got all the original system apps for. 30 if you want the netflix one only pm me
Sent from the batman
Click to expand...
Click to collapse
That could help!
PM sent.