I flashed my G1 following the directions on Cyanogenmods Full Update Guide for G1 on his wiki page. After failing the upgrade several times, I just decided to have my G1 get the T-Mobile OTA updates. I tried to flash the signed-kila-ota-148830.de6a94ca.zip update, and I got an error message that says "E:can't open /sdcard/update.zip (bad) Installation Aborted." I don't know what to do to fix this, other than wait for the OTA updates. Thanks in advance for any help you can offer.
I have an AT&T N1 that I bought second-hand a few weeks ago:
Android version 2.3.3
Baseband version 32.41.00.32U_5.08.00.04
Build number GRI40
There is no "lock" at the bottom of the screen when I boot the phone.
I have not received the OTA update to 2.3.4. I have tried the "checkin" procedure, but nothing. Menu/About phone/System updates says "Your system is currently up to date."
I followed widely available directions to manually upgrade to 2.3.4, but it didn't work. I saw several messages, ending with:
"E: No signature (226 files)"
"E: Verification failed"
"Zip verification failed!"
"Zip isn't signed correctly!"
"Installation aborted"
After reading through other threads, I am starting to think that I have a ROM that is somehow not stock or is carrier specific. Is my thinking right?
At this time I just want to get the regular, stock updates. Should I follow the directions in other threads to restore my phone to stock in order to get the regular stock updates?
A little more info:
Kernel version 2 [dot] 6 [dot] 35 [dot] 7 [dash] 59423 [dash] g08607d4 android [dash] build [at] apa28 #1
Follow the "Using PASSIMG.ZIP method" guide in the following link to bring the phone back to FRG83 (Android 2.2.1). After reboot, you should get the 2.3.4 update.
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
mwandaw said:
I have an AT&T N1 that I bought second-hand a few weeks ago:
Android version 2.3.3
Baseband version 32.41.00.32U_5.08.00.04
Build number GRI40
There is no "lock" at the bottom of the screen when I boot the phone.
I have not received the OTA update to 2.3.4. I have tried the "checkin" procedure, but nothing. Menu/About phone/System updates says "Your system is currently up to date."
I followed widely available directions to manually upgrade to 2.3.4, but it didn't work. I saw several messages, ending with:
"E: No signature (226 files)"
"E: Verification failed"
"Zip verification failed!"
"Zip isn't signed correctly!"
"Installation aborted"
After reading through other threads, I am starting to think that I have a ROM that is somehow not stock or is carrier specific. Is my thinking right?
At this time I just want to get the regular, stock updates. Should I follow the directions in other threads to restore my phone to stock in order to get the regular stock updates?
Click to expand...
Click to collapse
How are you trying to flash the update manually? Do you have a custom recovery? If so, you need to turn signature verification OFF...
Unfortunately, I cannot include links to outside websites in my replies. However, I can tell you that there are instructions on AndroidCentral [dot] com to manually update. The name of the post or article is "Nexus One's Android 2.3.4 update is here; we've got your update instructions".
Basically, the article has a link to a zip file with an awfully long name. I'm supposed to rename that to update [dot] zip and move it to the SD card in my phone. Then I'm supposed to get into the bootloader, select recovery and eventually select Apply sdcard:update [dot] zip. I did all of that without any trouble, but then I got messages below:
"E: No signature (226 files)"
"E: Verification failed"
"Zip verification failed!"
"Zip isn't signed correctly!"
"Installation aborted"
I tried turning off signature verification, but then the error message said something about a missing file.
I would be glad to wait for the OTA update, but at this point (three weeks since the announcement) I doubt that it will happen.
I would appreciate any advice.
What is the error about the missing file? Because assuming you just have a stock install, it should work fine. If you don't have a stock install and your carrier put a custom version on there, you won't be able to update using this. You would either have to do the passimg method mentioned above which will put you to the stock firmware and you should then be able to receive the update.
Otherwise, you will have to wait until your carrier comes out with an updated version.
It Worked!
I followed the "Using PASSIMG.ZIP method" guide recommended by madballs. It worked quickly and easily. About ten minutes after installing the stock Android 2.2 I received a message that a system update was available, and 2.3.4 installed without any trouble.
Hopefully, from now on I'll receive updates OTA quickly and without hassle.
Thanks!
mwandaw said:
I followed the "Using PASSIMG.ZIP method" guide recommended by madballs. It worked quickly and easily. About ten minutes after installing the stock Android 2.2 I received a message that a system update was available, and 2.3.4 installed without any trouble.
Hopefully, from now on I'll receive updates OTA quickly and without hassle.
Thanks!
Click to expand...
Click to collapse
You should not run into any problems from now on. When the next update comes, you can apply it manually or wait for the OTA. In addition, if at any time you try rooting your phone and flash a custom recovery and ROM, you can always use the PASSIMG method to go back to completely stock. There is a thread in the development section that linked a PASSIMG.zip file for to go to 2.3.4 directly. Never tried that file myself though. Enjoy your N1!
http://forum.xda-developers.com/showthread.php?t=1094018
I got my Incredible S (IS) successfully S-OFF using the beta of AlphaRev X.
I made the donation because the work the AlphaRev X have done is great
I used the http://forum.xda-developers.com/showthread.php?t=1122694 to install the clockworkmod and recovery, and it was completely successful. What I did is I obtain the right Clockworkmod Recovery for my IS I have now the ClockworkMod Recovery v4.0.0.1 on my Incredible S.
New the two problem I am facing is:
1- When I flash a language package (so that I will be able to read Arabic using the same original ROM which comes with the device) , the installing gets aborted and unsuccessful. Although, I used the same language packaged which I used it for my old Desire HD and now both are Froyo .
The message I gets on Recovery page is :
-- Installing : /sdcard/Arabic_DHD_2.2.1 _FIX_Browser_RTL. Zip
Finding update package…
Opening update package…
Installing update …
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the clockworkMod 3.0 Ginger bread based recovery. Please switch to Edify scripting (updater-script and update-binary) to create working update Zip Package .
Installation aborted
Well, I don’t know what that all mean and I don’t know how I would fix this. It seems so complicated
Please would any Developer out there help!
2- I tried to flash a custom ROM by LeeDrOiD_HD_V 2.2.3, but also didn’t work. The message I gets is:
-- Installing : /sdcard/LeeDrOiD_HD_V2.2.3. Zip
Finding update package…
Opening update package…
Installing update …
Checking Model ID
Assert failed: getprop(“ro. product .device”) ==”
ace” II getprop (“ro.build.Product”)==”ace” II
getprop(“ro.product.board”) ==”ace”
E:Error in /sdcard/ LeeDrOiD_HD_V2.2.3. Zip
(Status 7)
Installation aboard.
Please would anyone of developer help me in getting this issue fixed. I really would appreciate it the effort and the reply. All I care about is the a ROM ( cocked or custom ROM) which can read Arabic and not losing the S-OFF I have been grated from AlphaRev X. thank you for your time and you support! I tried to post my question through the XDA web, but it refused. Please can you help me! Thanks for reading my email.
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Hardley97 said:
I have been tearing my hair out for about a week with this problem. I'm sure the answer is here somewhere, but I'm a novice and I don't understand phone developer vocabulary. Hopefully someone can link me to a solution to my problem.
I have a Verizon LG G2 (VS980 4G) and I'm trying to install CyanogenMod on it. Here's the info from the software page in settings:
Android version 4.4.2
Baseband version VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel version 3.4.0-perf [email protected]
Build number KOT49I.VS98024A
Software version VS98024A
I have followed these steps so far:
1. Rooted with towelroot
2. Installed SuperSU and BusyBox
3. Used AutoRec to install TWRP 2.7.0.0
4. Downloaded CM-10.2.0-vs980.zip to /sdcard/Download
When I boot into TWRP recovery and try to flash the zip from there, I get the following error message:
"assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip'
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip' "
And then when I try to reboot the system I get an error that shows the LG logo with the words "security error" underneath it, and the phone won't boot up. After that my only option is to do a factory hard reset, go back into TWRP and restore my backup.
When I bought the phone it was on Software version VS98027A, but I thought that might be the problem so I used the LG flash tool to download and flash the kdz file for VS98024A. This has not given me a new result, sadly.
I have read the install instructions on the CM page, but they describe an app called FreeGee, which I guess is supposed to install ClockworkMod. FreeGee says my phone isn't supported. CM's directions say if FreeGee doesn't work, I should use AutoRec, but they don't follow up with any TWRP-specific instructions. I have googled and youtubed for several days, but everything I find shows directions on how to root and install recovery, yet nothing on how to deal with this particular error message. Whenever I do find a thread that seems like it might be helpful, I can't understand the technical jargon involved.
Thanks in advance for any advice you can give.
Click to expand...
Click to collapse
Here's my advice, go back to stock again,the LG flash tool. When that completes, use Freedom Tools (its in Development) and use ioroot25 (link is in the aforementioned thread) to root device. Then use Freedom Tool to install twrp. I've used it many times and never had a problem. Re-download cm rom (perhaps bad download) and flash in twrp. I would suggest using a more current twrp (start with 2.7, DL newest twrp, flash, reboot recovery) then flash cm. Let me know how it goes!
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Hardley97 said:
Thanks for your help. I followed the ioroot and freedom tool steps no problem, but I don't know how to update twrp. The g2 isn't listed as a supported device on their website or in the twrp manager app. I searched the forum and found a thread about updating it, but every time I try to download the files, I get a message that says the download failed.
I downloaded a fresh copy of cyanogenmod and tried to flash with twrp2.7, but I got the same error message from my original post.
Click to expand...
Click to collapse
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
njstein said:
Huh, ok, well, first off here's the thread for twrp, make sure and flash the correct one for our device:
http://forum.xda-developers.com/showthread.php?t=2898705
Second, have you tried a different rom? I remember reading that jackpotcalvin's is the cm to use. Try his or a completely different one, just make sure and follow the op (some require different radios, just follow the op). But I would definitely upgrade twrp before trying anything else.
Click to expand...
Click to collapse
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Hardley97 said:
Okay, so thanks to the link you gave me, I have succeeded in updating TWRP to version 2.8.5.1. I tried once again to flash cm 10.2, with more error messages. Specifically, the error says:
assert failed: run_program("/system/bin/loki.sh") == 0
E:Error executing updater binary in zip '/sdcard/Download/cm-10.2.0-vs980.zip' (that line was in red text)
Error flashing zip '/sdcard/Download/cm-10.2.0-vs980.zip'
I chose that rom because it is the only one listed as stable on the CM page for the G2. This time it was a fresh download. After that failed, I looked up JackpotClavin and found this thread:
http://forum.xda-developers.com/showthread.php?t=2702958
But it might as well be written in Greek because I don't understand much of it at all. I don't think I'd be comfortable doing all the command line stuff without a video tutorial or a more layman-friendly set of directions. So I didn't try that one.
Then I just started browsing the Development forum for a rom with easy install directions and found this one:
http://forum.xda-developers.com/verizon-g2/development/rom-beanstalk-build-5-0015-t3001584
I followed the instructions and flashed it successfully, booted up successfully, and then I was bombarded with a never-ending series of popups that said Unfortunately, Google Play Services had stopped. So that Rom was unusable, but at least now I know that it is possible to flash a rom of some kind. I don't have my heart dead-set on CM, I just know that it's very popular and so I had hopes that it would be more stable than most. All I need is a stable rom that has working radios and the ability to use the native USB tether function without having to pay Big Red an extra fee for the privilege.
I have restored to stock 24A with TWRP 2.8.5.1. Any more pointers?
Thanks again for all your help. I can tell I'm making progress, just not sure how close I am to the light at the end of the tunnel.
Click to expand...
Click to collapse
Dude, I'm sorry for not reading closer to begin with, but ya, you're trying to flash a JB rom with a KK recovery. 2.7 and up are for kk only. I'm so sorry...
Did you flash a gapps zip with Beanstalk? Did you do a completely clean install?
If you still want to flash a 10.2 cm you're going to have to find the appropriate recovery, and there I'm of no use since I entered this phone on kk and don't know anything about its jb history. Also don't know about the USB tether part either (I don't use it) so you're probably going to have to do some searching, flashing, and experimentation.
But bright side is we've figured out why you couldn't flash the cm rom. Either stay on kk or above, or start scrolling through the dev section looking for jb recovery...
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Hardley97 said:
SUCCESS!
Last night I read a bit deeper into the CM11/12 thread and found a more noob-friendly breakdown of the directions on pages 4-6. I worked up my courage to dive into adb and it turned out to be easier than it looked. Another failed flash on the CM10.2 ROM left little doubt that the rom had to be the problem, and your last reply confirmed it. I went back to the CyanogenMod download page and grabbed a zip of CM11 and now I'm up and running!
Thank you so much again. I sent a donation to JackpotClavin, and I'd like to do so for you as well, if I could. I don't see a PayPal link in your signature, though.
Click to expand...
Click to collapse
So glad it worked for you and you're up and running!
Nah, bro, I'm good. Give it to the devs, they deserve it. Giving knowledge through experience is what xda is all about, pass it on when you can. Thank you, though!
Hi, I hope this is the right place to get help with this issue, if not I apologize, I'm new, this forum is huge, I'm not sure where I'd go for this.
Regarding my issue/background. I'm mildly savvy, I managed to successfully unlock my boot loader and install the Twrp boot recovery (version 3.0.2), and have installed SU. I have a couple app disablers and have disabled some what seem to be useless and, however they are system apps, I'm wondering if this may be the cause of the issue.
I've spent about 8 hours in total trying multiple different versions of the arm64, with basically this same error. At this point, and after much digging, I haven't been able to find a solution to my error anywhere.
Likely this is my own fault, but we will see. As stated above I'm trying to install the arm64 version on an HTC One m9 with twrp v3.0.2
The error I'm getting is E: Error executing updater binary in zip '/sdcard/xposed-v82-sdk22-arm64.zip
Any help is appreciated, I'm pretty sure it's something I'm missing. I'm going to keep trying to do this on my own but hey, if anyone has any advice,it is greatly appreciated!
AndroidWin said:
Hi, I hope this is the right place to get help with this issue, if not I apologize, I'm new, this forum is huge, I'm not sure where I'd go for this.
Regarding my issue/background. I'm mildly savvy, I managed to successfully unlock my boot loader and install the Twrp boot recovery (version 3.0.2), and have installed SU. I have a couple app disablers and have disabled some what seem to be useless and, however they are system apps, I'm wondering if this may be the cause of the issue.
I've spent about 8 hours in total trying multiple different versions of the arm64, with basically this same error. At this point, and after much digging, I haven't been able to find a solution to my error anywhere.
Likely this is my own fault, but we will see. As stated above I'm trying to install the arm64 version on an HTC One m9 with twrp v3.0.2
The error I'm getting is E: Error executing updater binary in zip '/sdcard/xposed-v82-sdk22-arm64.zip
Any help is appreciated, I'm pretty sure it's something I'm missing. I'm going to keep trying to do this on my own but hey, if anyone has any advice,it is greatly appreciated!
Click to expand...
Click to collapse
This error arises mostly due to two reasons:
you tried to flash a wrong .zip file that isn't designed for your system OR your recovery does not support it.
SDK21 is for Android 5.0.x
SDK22 is for Android 5.1.x
SDK23 is for Android 6.0.x
Maybe you could change your recovery (if you don't use the official one from TWRP's webpage.
You could also try to flash Xposed framework v80, which is known to work on most devices.
For further discussion and help, please use the official Xposed threads for Lollipop or Marshmallow, depending on your Android version.