When I was trying to flash a ROM, I encountered the following error message when I backed up the current ROM:
Reboot into Recovery:
Enter: POWER Key. Select : Vol UP / Vol Down
reboot system now
reinstall packages
delete all user data
format internal sd-card
Click to expand...
Click to collapse
-----------------------------
...
Not need checksum confirmation
-- Movi_check already executed!!...
-- movi-checking done!...
update media. finished.
-- Install from package...
Finding update package...
Opening update package...
E:Can't open /cache/Update.zip
-- Appling Muti-CSC..
Installing Multi-CSC
Installation aborted.
Click to expand...
Click to collapse
I had to reboot the system since I didn't know how to proceed. When I tried Root into Recovery, I got the same above error message. Why was it trying to deal with Update.zip which is supposed to be the file for rooting? I don't know if this is related or not: I'm currently with Bi-Winning, and I'm still having trouble mounting my phone with computer.
Any suggestions? All help is highly appreciated!
Related
so i did a nandroid restore.. downloaded the update and it fails with:
Finding update package...
I:Update location: CACHE:fumo/update.pkg
Opening update package...
I:Update file path: /cache/fumo/update.pkg
Verifying update package...
W:Can't verify META-INF/CERT.RSA
E:No signature (265 files)
E:Verification failed
Installation aborted.
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
slackwaresupport said:
so i did a nandroid restore.. downloaded the update and it fails with:
Finding update package...
I:Update location: CACHE:fumo/update.pkg
Opening update package...
I:Update file path: /cache/fumo/update.pkg
Verifying update package...
W:Can't verify META-INF/CERT.RSA
E:No signature (265 files)
E:Verification failed
Installation aborted.
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
I:Set boot command ""
Click to expand...
Click to collapse
Based on your errors (thanks for putting them all in there) it looks like you downloaded the update directly from Sprint (OTA), so you would think that the download itself was fine. But if it's saying it's not signed then the download must be corrupted. Try going back through the menu and saying firmware update again. If it says there isn't one available then you may need to delete update.pkg and reboot and try again.
Also just an FYI, Fresh ROM 4.0+ has the new update already in it.
ya.. ive was on modaco.. just didnt like it. is the fresh really that good?? i had problems with modaco when i goto edit a contact, it says social network not available, and doesnt let me edit it.
flipzmode said:
Based on your errors (thanks for putting them all in there) it looks like you downloaded the update directly from Sprint (OTA), so you would think that the download itself was fine. But if it's saying it's not signed then the download must be corrupted. Try going back through the menu and saying firmware update again. If it says there isn't one available then you may need to delete update.pkg and reboot and try again.
Also just an FYI, Fresh ROM 4.0+ has the new update already in it.
Click to expand...
Click to collapse
fresh rom 4.0+???? i only see 0.6b..
slackwaresupport said:
fresh rom 4.0+???? i only see 0.6b..
Click to expand...
Click to collapse
I meant it's been included since 4.0. Grab 0.6b if you like the blue theme (check the screen shots) or just 0.6 if you don't want the theme.
And you can't ask if I think it's that good... I make it.
slackwaresupport said:
ya.. ive was on modaco.. just didnt like it. is the fresh really that good?? i had problems with modaco when i goto edit a contact, it says social network not available, and doesnt let me edit it.
Click to expand...
Click to collapse
It is the best at the best at this time. With updates that are very praid . usually with in a few hours of changes
Hi, I have a friend who currently has
Android Recovery System <2e> on his droid. Wanting to know if there's a way to change from that to Amons? Also, while using the <2e> any zip he tries to install comes up with the error E: Can't open /cache/recovery/command
If he scrolls down to Apply sdcard: update.zip he gets:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification fialed
Installation aborted.
This happens when trying to open .zip's such as Evil Eris 2.0 or any other zip. I have Amon's recovery and these zips work fine for me.
Any and all help is appreciated. Thanks in advance.
was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....
No files/names have been changed. If I could get Amon's recovery I could mod his phone for him. I have Amon's and do not have this issue. It is prbably something I am not doing due to being unfamiliar with the recovery he has. Basicaly I think all I really need is a way to get his recovery to read Amon's and I'm good.
andrew8806 said:
was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....
Click to expand...
Click to collapse
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.
If his phone is rooted just download rom manager from the market, open it, scroll all the way to the bottom and hit flash alternative recovery.
That should do it.
.mak said:
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.
Click to expand...
Click to collapse
I change the name of update.zip and it always fails to verify.
Before anyone freaks on me asking for help i have tried all the other fixes and they dont work for my problem.
i havent deleted any apps, im rooted, i havent manually changed any files other than build.prop and i have already converted it back to original.
i HAVE had to resort to the chinese update to fix a problem from borked ubuntu install.
and here is a copy of the last part of my last_log
Code:
...
E: /dev/block/mmcblk1 does exist
Finding update package...
I:Update location: /cache/acer_ug/update.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is q690 bytes; signature 1672 bytes from end
I:whole-file signature verified
::verify_file returned 0
Installing update...
Verifying current system...
contents of partition "/dev/block/mmcblk0p2" didn't match EMMC:/dev/block/mmcblk0p2:3094528:############################################################# file "EMMC:/dev/block/mmcblk0p2:3094528:#############################################################" 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("EMMC:/dev/block/mmcblk0p2:3094528:#############################################################")
assert failed: apply_patch_check("EMMC:/dev/block/mmcblk0p2:3094528:#############################################################")
E:Error in /cache/acer_ug/update.zip
(status 7)
Installation aborted.
just for ease of retyping i replaced the long list of numbers/alpha with ### each instance is the same identical numbers on my log though.
after it tries to install the update i get the triangle and then reboots to the way it was prior.
Your boot partition / kernel (/dev/block/mmcblk0p2) doesn't match what the update expects. Have you by any chance flashed the chinese update before?
adancau said:
Your boot partition / kernel (/dev/block/mmcblk0p2) doesn't match what the update expects. Have you by any chance flashed the chinese update before?
Click to expand...
Click to collapse
Before anyone freaks on me asking for help i have tried all the other fixes and they dont work for my problem.
i havent deleted any apps, im rooted, i havent manually changed any files other than build.prop and i have already converted it back to original.
i HAVE had to resort to the chinese update to fix a problem from borked ubuntu install.
and here is a copy of the last part of my last_log
[log]
after it tries to install the update i get the triangle and then reboots to the way it was prior.
Click to expand...
Click to collapse
10char..........
n1nj4dude said:
i HAVE had to resort to the chinese update to fix a problem from borked ubuntu install.
Click to expand...
Click to collapse
Then use the fix given in the Chinese update.zip thread!
working on it... its not exactly plain english for those of us new to the whole android thing.
thanks....
Hello,
I have a rooted tf300t and I'm trying to update it to the JB . And I really need some kind of " Step by Step from scratch" guide,
Can anyone be my light in this moment of darkness?
tks:good:
Download the JB firmware here
http://forum.xda-developers.com/showthread.php?p=27095558 under "Asus firmware"
And flash that bad boy in recovery.
Sent from my Nexus S 4G using Tapatalk 2
luizfpg said:
Hello,
I have a rooted tf300t and I'm trying to update it to the JB . And I really need some kind of " Step by Step from scratch" guide,
Can anyone be my light in this moment of darkness?
tks:good:
Click to expand...
Click to collapse
There is a step by step easy thread, it's general and pretty much has the same thread headline as yours. Look for it and you'll be updated
Sent from my SGH-T989 using xda app-developers app
DMardroid said:
Download the JB firmware here
http://forum.xda-developers.com/showthread.php?p=27095558 under "Asus firmware"
And flash that bad boy in recovery.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I've donwloaded the file via Asus site, but now I don't know what to do next.
luizfpg said:
I've donwloaded the file via Asus site, but now I don't know what to do next.
Click to expand...
Click to collapse
Extract it.
There should be another zip in there. That's the one to flash.
Sent from my Nexus S 4G using Tapatalk 2
DMardroid said:
Extract it.
There should be another zip in there. That's the one to flash.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Worked!!! The problem ig that I wasn"t extracting properly.... Thanks..
luizfpg said:
Worked!!! The problem ig that I wasn"t extracting properly.... Thanks..
Click to expand...
Click to collapse
Hi, could you please tell me where can i find a guide on how to flash my device with JB software. I'm in Europe,with EU TF300.
EDIT: I DID THAT:
Finally found a workaround for the "not finding any update".
1: download the dlpkgfile and command file found here on the forum.
2: use a file manager with root permissions (eg:es file explorer)
3: copy the dlpkgfile to /cache and the command file to /cache/recovery.
4: temp unroot with the Voodoo app
5: restore original build.prop
6: reboot in recovery (hold power + volume down) untill the white text appears telling you to press volume up to enter recovery
7: auto installs
8: reboot + reroot with the voodoo app
Failed after step 7.
Same way as with Official automatic update which failed and I am unable to repeat it... please help
EDIT2:
The log file says:
Code:
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13104069
Verifying current system...
file "/system/bin/iptables" 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/bin/iptables", "c17d0e858fb71cd4886f765f26ac4371d6a875d5", "9a6180a19d373e64857d81942acc2d2544bd65b7")
assert failed: apply_patch_check("/system/bin/iptables", "c17d0e858fb71cd4886f765f26ac4371d6a875d5", "9a6180a19d373e64857d81942acc2d2544bd65b7")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.
I:timed out waiting for key input; rebooting.
OK
I have a Nexus 7 with Android 4.1.2 ( JZ054K) and the damn thing wont install any Rom i load onto it.
I copied the text from recovery menu, maybe someone here can help me with that.
finding update package...
opening update package...
Installing update...
verifying current system...
assert failed: apply_patch_check("/system/app/phonesky.apk", "a7d39ad7438b0fb6347033a75b5d5054aae9bfa8", "0178827dead56e73ece35ffa29345bf3793b842a")
E:Error in /sdcard/c01f18e07f87.signed-nakasi-JOP40D-from-JZ054K.c01f18e0.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open Rom Manager to report the issue.
Also, even though my Nexus 7 is still 4.1.2 i dont get any update notifications from google, and checking for system updates says that the device is up to date.
Pr0xY42 said:
I have a Nexus 7 with Android 4.1.2 ( JZ054K) and the damn thing wont install any Rom i load onto it.
I copied the text from recovery menu, maybe someone here can help me with that.
finding update package...
opening update package...
Installing update...
verifying current system...
assert failed: apply_patch_check("/system/app/phonesky.apk", "a7d39ad7438b0fb6347033a75b5d5054aae9bfa8", "0178827dead56e73ece35ffa29345bf3793b842a")
E:Error in /sdcard/c01f18e07f87.signed-nakasi-JOP40D-from-JZ054K.c01f18e0.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open Rom Manager to report the issue.
Also, even though my Nexus 7 is still 4.1.2 i dont get any update notifications from google, and checking for system updates says that the device is up to date.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1907796
Pr0xY42 said:
I have a Nexus 7 with Android 4.1.2 ( JZ054K) and the damn thing wont install any Rom i load onto it.
I copied the text from recovery menu, maybe someone here can help me with that.
finding update package...
opening update package...
Installing update...
verifying current system...
assert failed: apply_patch_check("/system/app/phonesky.apk", "a7d39ad7438b0fb6347033a75b5d5054aae9bfa8", "0178827dead56e73ece35ffa29345bf3793b842a")
E:Error in /sdcard/c01f18e07f87.signed-nakasi-JOP40D-from-JZ054K.c01f18e0.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open Rom Manager to report the issue.
Also, even though my Nexus 7 is still 4.1.2 i dont get any update notifications from google, and checking for system updates says that the device is up to date.
Click to expand...
Click to collapse
\
Read the guide aobove