Related
Hi I'm new and sorry if this has been asked and solved somewhere but I've failed to find it using the forum search and through Google.
I'm trying to flash SuperBadCM5 and get the error "E: Can't find update-script" .. "Installation aborted".
The update-script file is called "updater-script", but is in the correct directory. I've tried renaming it to update-script and then get a "(bad)" error upon trying to flash it. I'm doing this from JF v1.41 (RC8) and HardSPL.
Any help for getting this or any other ROM to work quickly would be greatly appreciated as I'm stuck with 1.00 firmware right now and can't do much on my phone..
Thanks.
Hi,
I have an odd problem. I have rooted my nexus S and am on 2.3.2, and have clockwork recovery. however in order to apply the update to 2.3.3, it doesnt not work with clockwork recovery, and so I was trying to flash stock recovery using a recovery.img file from one of the stock nandroids on the site.
when I am in bootloader, and i try fastboot flash recovery recovery.img where this is the stock recovery image, it gives me a "remote: Write Fail" error.
However I have no problem in using the same command to flash clockwork recovery image.
Does anyone know why this is happening? and does anyone know how i can flash the stock recovery image back to my phone so I can apply the update to 2.3.3?
Thanks,
brownmonkey said:
Hi,
I have an odd problem. I have rooted my nexus S and am on 2.3.2, and have clockwork recovery. however in order to apply the update to 2.3.3, it doesnt not work with clockwork recovery, and so I was trying to flash stock recovery using a recovery.img file from one of the stock nandroids on the site.
when I am in bootloader, and i try fastboot flash recovery recovery.img where this is the stock recovery image, it gives me a "remote: Write Fail" error.
However I have no problem in using the same command to flash clockwork recovery image.
Does anyone know why this is happening? and does anyone know how i can flash the stock recovery image back to my phone so I can apply the update to 2.3.3?
Thanks,
Click to expand...
Click to collapse
CWM will apply the signed 2.3.3 update without a problem - what issue are you having where you can't apply through CWM?
krohnjw said:
CWM will apply the signed 2.3.3 update without a problem - what issue are you having where you can't apply through CWM?
Click to expand...
Click to collapse
so I downloaded the update and changed the filename to update.zip and put it in the root of /sdcard/
then when I boot into clockwork mod recovery, and click "apply update from sdcard" it starts running and after getting to verifying current system i get the following error
assert failed: apply_patch_check("/system/build.prop",...)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
and idea what is causing the problem? im a complete noob when it comes to this stuff
brownmonkey said:
so I downloaded the update and changed the filename to update.zip and put it in the root of /sdcard/
then when I boot into clockwork mod recovery, and click "apply update from sdcard" it starts running and after getting to verifying current system i get the following error
assert failed: apply_patch_check("/system/build.prop",...)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
and idea what is causing the problem? im a complete noob when it comes to this stuff
Click to expand...
Click to collapse
Yeah - it's checking build.prop and it's either been modified or you are not running a stock rom.
It's going to check quite a few files in the system partition and verify they match what it's expecting (as it is patching them) before it performs the update. If they don't match it will not proceed and you will get an assert failed error. This is not a boot loader problem, rather a file problem.
Did you apply anything that would have updated build.prop?
krohnjw said:
Yeah - it's checking build.prop and it's either been modified or you are not running a stock rom.
It's going to check quite a few files in the system partition and verify they match what it's expecting (as it is patching them) before it performs the update. If they don't match it will not proceed and you will get an assert failed error. This is not a boot loader problem, rather a file problem.
Did you apply anything that would have updated build.prop?
Click to expand...
Click to collapse
Yes i did, I added in a few lines to increase my download speeds, and set it so that it always locks to hspa... if i remove the lines and resave build.prop file should that fix the issue and allow me to update?
brownmonkey said:
Yes i did, I added in a few lines to increase my download speeds, and set it so that it always locks to hspa... if i remove the lines and resave build.prop file should that fix the issue and allow me to update?
Click to expand...
Click to collapse
So i tried the above... i removed the two extra lines I had added to build.prop and tried the update but it still gives the same error? Do you know of any way I can get around this error or is the only way to do a titanium backup and flash the stock 2.3.3 version that has been posted in another link?
Thanks for your quick replies.
You may be able to flash the full update. Or get a build.prop from a 2.3.2 build if someone can pull it.
Sent from my Nexus S using XDA Premium App
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
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?
Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
Code:
...
....
Source: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS254 : user/release-keys
Target: oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys
Verifying current system...
Package expects build fingerprint of oneplus/bacon/A0001/6.0.1/MHC19Q/ZNHKAS254 : user/release-keys or oneplus/bacon/A0001: 6.0.1/MHC19Q/ZNH2KAS2X1 : user/release-keys;
this device has oneplus/bacon/A0001: 5.1.1/LMY48B/YOG4PAS1NO: user/release-keys
Updater process ended with ERROR: 7
Error installing zip file '@/cache/recovery/block.map
...
...
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!
Sopis said:
Hi Everyone
Can anyone please stop my suffering? I tried everything and I am lost...
My phone kept asking me to update to KAS254 which I finally managed to do by flashing stock recovery...but now it is giving me another OTA, some weird alphanumeric combination, around 60MB.
Thing is I cannot update it and the update keeps popping up and I am going crazy already.
TWRP returns this log:
So appearently, I still have some Android L leftovers, but I don't know what that is.
Could anyone please help? I am going nuts!!
Thanks XDA!!!
Click to expand...
Click to collapse
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.
Durso81 said:
You can not do OTA with a customer recovery like TWRP. If you want the latest stock firmware you will need to download the latest from https://cyngn.com/support and flash all the files via fastboot then reinstall TWRP and SuperSU for root.
Click to expand...
Click to collapse
hi, thanks for your reply..I did that but it did not work
Sopis said:
hi, thanks for your reply..I did that but it did not work
Click to expand...
Click to collapse
What do you mean did not work? What happen when you flashed all the stock files via fastboot?
are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..
Sopis said:
are you saying that I should apply the downloaded file via fastboot?
what I did is downloaded the recovery and updated to KAS54, then another update popped up and again I cannot update...no I get the same error, but this time it says I have KAS254 and the package expects something newer..
Click to expand...
Click to collapse
Are you running stock recovery or twrp? Cause your title says twrp.
hey, I got it finally..thanks for the effort...thread can be deleted