I've done so many searches and everyone who seems to be having this problem all found different solution. I'm positive it wasn't my download. I did MD5 checks and everything =/ It's still giving me the error.
Again, here's the error:
--Install: /emmc/Xoom-Universal-Root.zip
Finding update package...
Opening update package...
E:Can't open /emmc/Xoom-Universal-Root.zip
(bad)
Installation Aborted
Click to expand...
Click to collapse
Any help is appreciated! I just unlocked and flashed recovery EOS CWM R6
same problem
Hi There,
I am at the exact same stage and the exact same problem.
I thought formatting the sd card to fat would do it, but am disappointed.
Did you figure it out?
Regards,
Dom
draikz said:
I've done so many searches and everyone who seems to be having this problem all found different solution. I'm positive it wasn't my download. I did MD5 checks and everything =/ It's still giving me the error.
Again, here's the error:
Any help is appreciated! I just unlocked and flashed recovery EOS CWM R6
Click to expand...
Click to collapse
If you have successfully unlocked and installed a custom recovery, flashing a custom rom like Eos will give you root. Are you wanting only root and custom recovery running stock rom and kernel?
I was hoping to put wingray on it.
I must give that a go, will let you know how I got on.
Got it finally, it was looping for a while but when I wiped the data and a factory reset which did the job.
Thanks man
Related
Hey guys, ive been trying to get my Captivate to reboot into clockworkmod, and it has been an utter failure.
After i choose the "Reinstall Packages" option I get a message:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have tried to choose the option hundreds of times and i yet have no luck. All of this have been done with the ROM manager app on the android market.
Please help since I cant install any custom ROM without it
same thing over here
farooq88 said:
same thing over here
Click to expand...
Click to collapse
pandakh said:
Hey guys, ive been trying to get my Captivate to reboot into clockworkmod, and it has been an utter failure.
After i choose the "Reinstall Packages" option I get a message:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have tried to choose the option hundreds of times and i yet have no luck. All of this have been done with the ROM manager app on the android market.
Please help since I cant install any custom ROM without it
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1052991
pandakh said:
Hey guys, ive been trying to get my Captivate to reboot into clockworkmod, and it has been an utter failure.
After i choose the "Reinstall Packages" option I get a message:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have tried to choose the option hundreds of times and i yet have no luck. All of this have been done with the ROM manager app on the android market.
Please help since I cant install any custom ROM without it
Click to expand...
Click to collapse
Read forums.
GOD nothing seems to work...I know it is a lot of trouble but i would be forever grateful if someone walked me through the easiest way. PLEASE HELP! i want a custom ROM...ps im a super noob
pandakh said:
GOD nothing seems to work...I know it is a lot of trouble but i would be forever grateful if someone walked me through the easiest way. PLEASE HELP! i want a custom ROM...ps im a super noob
Click to expand...
Click to collapse
If you haven't found help yet, I can assist. maybe through IM or something. I have done this countless times.
jack man said:
If you haven't found help yet, I can assist. maybe through IM or something. I have done this countless times.
Click to expand...
Click to collapse
Do you think its wise for him to flash a custom rom if he cant figure out why hes getting the signature failure?
Not trying to be a **** here.. but you should really read through the forums and then read them again before you start flashing custom roms.. Just saying.
erbsmokah said:
Do you think its wise for him to flash a custom rom if he cant figure out why hes getting the signature failure?
Not trying to be a **** here.. but you should really read through the forums and then read them again before you start flashing custom roms.. Just saying.
Click to expand...
Click to collapse
valid point. +1
You have to re-install packages twice before cwm takes. And the update.zip on the root of the SD
If then it doesn't take, delete the update.zip. then flashclockwork again via RM and make sure the update.zip is again on the internal SD. then try reinstall packages twice. again. Worked everytime for me. Should be same for you
sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch
rwells813 said:
You have to re-install packages twice before cwm takes. And the update.zip on the root of the SD
If then it doesn't take, delete the update.zip. then flashclockwork again via RM and make sure the update.zip is again on the internal SD. then try reinstall packages twice. again. Worked everytime for me. Should be same for you
Not with a failed signature verification. That means he's on 3e recovery and needs to flash a different kernel in order to get CWM recovery. I agree that if you don't read the forums and know this flashing will lead to trouble.
sent from SGS Captivate 2.3.4 with CM7 or MIUI using Escapist or TKglitch
Click to expand...
Click to collapse
sent from my Gingerbread Cappy using Tapatalk from somewhere on AT&T's ****ty network.
Meeh i found out what my problem was, and i am ashamed. I was using a new computer and i had downloaded the drivers but i hadnt installed them.And i needed that to use the modded version of the loader to avoid the sig checks. Before i found out I reflashed to stock eclair to avoid the signature problem, and there i realized i was dumb. thanks for the help...running serendipity 6.4 not bold enough to run serendipity 7 because its gb based
alright... i was recently soft-bricked, then got everything fixed, up and running, spent a day on stock making sure everything would work correctly... it did.
This morning, i rooted, got SU installed, and setCPU running, so root is fine... but heres what happens when i try to load into recovery:
3-finger boot
-- Movi_check Start..!!
checksum confirmation nned_checksum[0]
Not need checksum confirmation
-- Movi_check already executed!!..
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
Install default apk-files, please wait
Install default apk-files, finished
Click to expand...
Click to collapse
from this point i use the volume keys to select "reinstall packages"
then i get this:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Click to expand...
Click to collapse
_________________________________________________
...anyone have any idea what this means... or what to do?
Working with the stock blue 3e-recovery.
Looks like you need to re install modded 3e recovery. The Super Thread in the Dev section has links to the download for it. That or you can use SGS kernel flasher to flash the Froyo CWM kernel (assuming your on Froyo/stock). Also found in the Super Thread. Good Luck!
xIC-MACIx said:
Looks like you need to re install modded 3e recovery. The Super Thread in the Dev section has links to the download for it. That or you can use SGS kernel flasher to flash the Froyo CWM kernel (assuming your on Froyo/stock). Also found in the Super Thread. Good Luck!
Click to expand...
Click to collapse
alright, got the community kernel installed and green-cwm working, but still having the same issue... Every time I try to install miui 1.11.25, it aborts and says, (bad)
I know the download is good, /system is mounted and I do every thing normally, but it just wont install... I don't get it.
Ph0z3 said:
alright, got the community kernel installed and green-cwm working, but still having the same issue... Every time I try to install miui 1.11.25, it aborts and says, (bad)
I know the download is good, /system is mounted and I do every thing normally, but it just wont install... I don't get it.
Click to expand...
Click to collapse
Maybe you have to mount storage partrition? Oh nvm you did lol. Try downloading again.
Ph0z3 said:
alright, got the community kernel installed and green-cwm working, but still having the same issue... Every time I try to install miui 1.11.25, it aborts and says, (bad)
I know the download is good, /system is mounted and I do every thing normally, but it just wont install... I don't get it.
Click to expand...
Click to collapse
I've never flashed MIUI from green CWM before, only red. Maybe try a diff download link or Galnet? Are you wiping data,dalvik, and cache before flash? Also, is the zip on your internal SD card? Sorry for the 20 questions lol
Ryanscool said:
Maybe you have to mount storage partrition? Oh nvm you did lol. Try downloading again.
Click to expand...
Click to collapse
I've downloaded like 15 times now from both my phone and comp. Tried to, flash from blue, red, and green... Still says bad.
xIC-MACIx said:
I've never flashed MIUI from green CWM before, only red. Maybe try a diff download link or Galnet? Are you wiping data,dalvik, and cache before flash? Also, is the zip on your internal SD card? Sorry for the 20 questions lol
Click to expand...
Click to collapse
I don't want to flash galnet... Thats what caused me to brick in the first place... Well... Trying to flash out from there. Everyone said flash miui 11.25 right over the latest galnet and they had no issues, I bricked. So I'm trying to assess what went wrong, and get it installed.
Hello,
I wanted to upgrade from 4.4 to 4.4.2 through recovery.
The thing is that I took the wrong file and got a "failed to verify whole file signature" error when I "adb sideloaded".
I finally succeeded installing the 4.4.2 but I am wondering if I should clean somehow the phone as some files (from the wrong update file) were sent to the device and the upgrade was aborted.
Thanks
rarat said:
Hello,
I wanted to upgrade from 4.4 to 4.4.2 through recovery.
The thing is that I took the wrong file and got a "failed to verify whole file signature" error when I "adb sideloaded".
I finally succeeded installing the 4.4.2 but I am wondering if I should clean somehow the phone as some files (from the wrong update file) were sent to the device and the upgrade was aborted.
Thanks
Click to expand...
Click to collapse
If the upgrade was aborted, there is nothing to clean up. It validates the file first before it attempts to flash. So, the flash hasn't started by then.
You should be good
jj14 said:
If the upgrade was aborted, there is nothing to clean up. It validates the file first before it attempts to flash. So, the flash hasn't started by then.
You should be good
Click to expand...
Click to collapse
Thanks for the reply. I thought some files would have to be uploaded solewhere before it can verify the signature.
So I posted ages ago about my phone having ROM loading issues, it no longer loads any ROMs. I have been told to flash 4ext again but i cannot find a tutorial on how to flash via fastboot, and i need help, i cant find links for 4ext to flash or any guides on how to do it, just how to update via the app on the phone, but, like i said, the phone has no rom so i cant reset my recovery.
sid.parmar said:
So I posted ages ago about my phone having ROM loading issues, it no longer loads any ROMs. I have been told to flash 4ext again but i cannot find a tutorial on how to flash via fastboot, and i need help, i cant find links for 4ext to flash or any guides on how to do it, just how to update via the app on the phone, but, like i said, the phone has no rom so i cant reset my recovery.
Click to expand...
Click to collapse
step 2 only
http://forum.xda-developers.com/showthread.php?t=1631861
cheers, will this be do-able on mac, as this is the only computer i have right now, i followed lifehackers instructions on how to install ADB and fastboot.http://www.lifehacker.co.uk/2014/06/06/install-androids-adb-fastboot-tools-os-easy-way and i just want to know that i dont have to get my friends pc
sid.parmar said:
cheers, will this be do-able on mac, as this is the only computer i have right now, i followed lifehackers instructions on how to install ADB and fastboot.http://www.lifehacker.co.uk/2014/06/06/install-androids-adb-fastboot-tools-os-easy-way and i just want to know that i dont have to get my friends pc
Click to expand...
Click to collapse
i don't know if it works on mac but you can try it
tried it on pc, still the same problem
the screen says the following when flashing anything
finding update package...
opening update package...
install update...
E:Error in/sdcard/cm-11/20140606/Sultan-pyramid.zip
(Status 0)
Installation Aborted
Im trying to flash the new CM 11
sid.parmar said:
tried it on pc, still the same problem
the screen says the following when flashing anything
finding update package...
opening update package...
install update...
E:Error in/sdcard/cm-11/20140606/Sultan-pyramid.zip
(Status 0)
Installation Aborted
Im trying to flash the new CM 11
Click to expand...
Click to collapse
try this version of 4ext
http://www.4shared.com/zip/DVRZ3fiwba/4EXT_Recovery_Touch_v1006_RC2.html
it is the latest
just extract the recovery.img from the zip and flash it via fastboot command
it worked! cheers, seems like recovery needed an update
sid.parmar said:
it worked! cheers, seems like recovery needed an update
Click to expand...
Click to collapse
i knew that the recovery version was the issue
but i forgot to give you the latest version in first place
I had pretty much the same error but do you think flashing the latest recovery will work for CWM recovery as well?
Have you tried installing 4EXT Recovery Updater apk from it's site?
Hi Guys,
I have tried many of the ROMs available however, for the most part, I get this error "error executing updater binary" in TWRP. I have also tried CWM and Philz recovery. The only ROM that installs is CM11. Does any one know what is the issue? Anyone got a solution? Thanks.
Current Recovery: TWRP 2.7.1.1
I'm the only one experiencing this issue?
Specifically which ROMs have you tried?
Transmitted via Bacon
I've tried the following:
AOSP from the Oneplus homepage
AOSP flapped
mahdi-rom
Team GUMMY
Are you checking the md5 when you download?
Transmitted via Bacon
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
bill1clinton said:
No, I did not. However, having said that, would it really be the case of corrupt downloads across multiple roms? As well, CM11 installs perfectly fine.
I'll do some checking now.
Click to expand...
Click to collapse
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Well, just re-downloaded AOSP from the oneplus homepage and flapped AOSP. I also checked their md5 hashes; they match. I will report back.
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
timmaaa said:
It's possible, I'm just throwing out the usual causes of your problem. It wouldn't be the first time it's happened.
Transmitted via Bacon
Click to expand...
Click to collapse
Just tried to flash both, both times I get the "error executing updater binary" error. I do not have the technical expertise to try to correct this.
Anyone else with any ideas?
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
demkantor said:
Unzip the ROM that works and the ROM that doesn't with 7zip, then swap the update-binary from the working to the non. Rezip (set to store) then either sign the ROM or toggle SIG verification in recovery, then make nandroid, wipe clean, flash
By the way, what version do you have? 16 64? Chinese? Can you get bootloader info?
Click to expand...
Click to collapse
The ROM that works is CM11 nightly and the one that I would like to install is pure AOSP. Are you certain that their update binary files would/could be interchangeable?
And how to do you "set to store"? I use 7zip.
I have the international 64GB. And I am not sure how to check my bootloader.
I really do apologize for my newb-ness on this matter.
There shouldn't be an issue, but of course I can't promise as I don't know what specifically is going on in your case
When you choose zip, there you will have different compression options, choose store
Try
fastboot oem device-info
Write down output here
No worries, we all are noobs in our own ways
did anyone figure this out? im having the same issue trying to install lollipop roms
Same problem here
jlinn75 said:
did anyone figure this out? im having the same issue trying to install lollipop roms
Click to expand...
Click to collapse
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
viriatis said:
Hi have same problem here.
my Bootloader is unlocked, I have phone rooted, I use last bacon twrp version. I already clean all phone.
I could install any rom, finally I found cm-11.0-XNPH44S-bacon-signed-fastboot.zip with fastboot.bat file that helped me to recover my phone.
I did all steps from all guys I searched, I can't know why I always appear error "error executing updater binary".
I tried cm-12-20150124-NIGHTLY-bacon.zip, I tried BlissPop-v1.8-bacon-OFFICIAL-20150123-2230.zip, all same error. I also tried to install original cm-11, same error.
I don't know what to do more or why? I checked Bootloader is unlocked.
Click to expand...
Click to collapse
I get the exact same error, as you I can only flash CM-11, strange cause I was running Euphoria OS Lollipop!
Someone must know the cause!
sad problem
doe or die said:
I'm getting this same message, except I'm getting it when trying to install the new OTA update. I'm rooted with custom recovery, but haven't flashed any ROM. After I download the update, I push "install update" and my phone reboots into TWRP to install the update, and then gives me the "error executing updater binary" error. I tried downloading the update manually off the web and installing it via TWRP on my own, but it gave me the same message. Not really sure what else to do at this point.
Click to expand...
Click to collapse
I'm having exactly same problem. So is this common problem or what? I had multirom and xposed framework but after uninstalling them both I get the same error again. I hope this does not happen when we are getting the Lollipop-update. Sry for bad enklish.
Anyone help?