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.
Related
Ok, I have a phone with unlocked boot loader and FRF50 on it.
I put the original system recovery on (it had another prior to my ownership), but when the OTA update arrives, I get the following error:
Verifying current system...
assert failed: apply_patch_check("/system/framework/am.jar", "efccd3...:, ea...: )
E: Error in /cache/836691a1ca8b.signed-passion-FRF91-from-FRF50.836691a9.zip
(Status 7)
Installation aborted...
Any ideas???
Thanks!!!
have you tried doing the line of updates start from frf50 then do frf83 then frf83b then do frf91
No, but based on the error it looks like it was trying to go from FR50 (installed) to FRF91 based on the update file name....
I'm not doing this manually, I'm letting the OTA update take care of it....
Can you point me to the update images? I'd like to get it to do OTA updates again, but if I have to do manual I guess I'll deal with it...
I wonder if it is a problem with the v 2E recovery?
Hey Pete,
I am getting the exact same issue with my nexus over here in Oz. I jumped on the early release and manually installed and now it wont update from frf50-frf91 OTA with the above error.
Very frustrating. I wondered if a wipe data/factory reset then wait for another OTA might work. I am unsure of exactly how much that will affect the phone though. I would rather not lose pictures and movies on the SD card and apps would be a PITA to get back on with my settings.
Maybe the manual updates might be a good place to start.
What version of the recovery do you have on your phone?
pwkpete said:
What version of the recovery do you have on your phone?
Click to expand...
Click to collapse
I am a bit of a noob Pete when it comes to Android and Nexus. I am not sure on the version or even how to check. Can you give me a hint ??
I have an un-rooted stock phone which I downloaded the FRF 50 update to when it first came out. I have made no other changes to it.
Give me a call centre skills based routing or call recording system and I'm your man, but smart phones are not in my skillset... I am trying to learn though. I just learnt what the ADB is.
you are on stock recovery and rom...and you wont anything in your SD card it doesnt wipe sdcard, only the phone setup, and if you have the backup feature on phoen you wont really lose the apps either
you can always do the #*#CHECKIN#*# on dial pad then go to settings and check for updates to see if you can get the OTA
i did it mainually it i couldnt wait any longer for the OTA.. so its not really hard to do it maunally lol
Even if I do that with my FRF50 phone, it just says success...
It took a week for the OTA update to reattempt an install. (and fail)
I did download a full signed FRF91 which I'm going to try applying soon, I hope after that OTA's will just be automatic...
Fixed at last !!!
I went through this forum.xda-developers.com/showthread.php?t=717870
Which took me back to epe76. I then went to frf85b with a link further in the same thread and got an instant OTA update to frf91.
YAY FIXED !!!!!!!!!!!!!!!!!!!
Forgot to post here, I downloaded the complete FRF91 signed and just installed it. Contains everyting including radio.
I don't have the link anymore, but I recall it contained the words, "FRF91", "signed", "passion"....
That should get you there...
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 looked through a plethora of forum posts and none of them seem to fix my problem so please forgive me if maybe I missed a post. I have a Sprint HTC One and I was running Viper One 3.5 (Android 4.3 w/ Sense 5.5) and I wanted to upgrade to 4.4 Kit Kat. I've found a couple ROMs that I liked and flashed no problem. They all had their issues that I couldn't live with so I looked for a more credible developer. I found a kit kat ROM from AOPK and ive been trying to flash it but I constantly keep getting errors. I am running TWRP 2.6.3.0. Here is what the errors look like:
-------------------------------------------------------------------------
ROM Error:
"symlink: some symlinks failed"
"E: Error executing updater binary in zip /sdcard/...
"Error flashing zip"
GAPPS:
"file_getprop: failed to stat "/system/build.prop..."
"E: Error executing updater binary in zip"
"Error flashing zip"
--------------------------------------------------------------------------
All of these errors are logged from one screen at one time. In other words, they aren't different errors i've been getting, they are from the same flash. This is just a brief description of the logged errors. I left out the sd card directories, etc. The reason I include the Gapps error is because on time when I flashed the ROM, it said successful but no log of anything happening so I went on to flashing Gapps and got the error above. If anyone can help that would be GREATLY appreciated. Thank you so much for your help and time. :good: Sorry for the long post, just trying to describe the entire problem so we can get a better/more precise solution. THANKS!
I get this 2016-06 Patch that wants to be installed on my Nexus 6. When I try to install it, the ERROR screen shows during the process. This happens over and over. As painful as it was, I did a factory reset on my phone and the issue still exists.
I contacted Google, because it is a Google phone and has Android, and they routed me to Motorola.
Motorola gives me this update tool which does not solve the issue.
Since it is more than 1 year old, there is no warranty even though it is not my fault at all that the 2016-06 patch does not update properly.
First, Motorola support for this device sucks. Second, any ideas to resolve this since Motorola support for this device sucks?
with your positive attitude, its hard to believe that Motorola doesn't want to go out of their way to help you..
its out of warranty, so don't expect anything support wise..
What error, on what screen? Which version do you have? Are you unlocked? Do you have a custom recovery? Are you rooted?
Do you have a computer, and did you try to sideload the OTA?
@brucechidester you need to give more information if you need help solving the issue. it could me one of very many things btw..
Answer to questions
I wish Motorola would have asked as good as questions as you have. What screen? During the upgrade process it appears to be loading properly until the error screen shows with an Android dead and the word "error" above him. What version? 6.0.1. Is a system unlocked? It had been unlocked in the past but this process was reversed and the screen shows the key in the locked position. Sideload the OTA? I am not familiar with this process so I would say not. Motorola had me install a Windows application which attempted to upgrade the firmware via USB but this did not resolve the problem. This was Motorola's only technical response to my problem. This did not work so they gave up.
Okay, then I suggest, you should look up the Nexus 6 Index thread
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
and read the The Nexus 6 All-In-One Beginner's Guide, and particularly the Nexus 6 OTA Help Desk .
After that we'll be able to speak the same language, and help you if you get stuck, because you'll be able to ask specific questions.
I attempted to update the phone using the sideload OTA process. It gets to about 47%, quits and gives an error. I definitely have a Nexus 5 and used the hammerhead image. A couple to be exact. Same result.
I noticed at the top when I got into to recovery screen:
Android Recovery
google/shamu/shamu
6.0.1/MMB30G/2756603
From this I assume I have update MMB30G
I found the update file for MMB30G identified at https://gist.github.com/jduck/53dc121820f6b30374bfa871146ca956
When I tried to update with this I get:
Installing update...
Source: google/shamu/shamu:6.0.1/MMB30G/2756603:user/release-keys
Source: google/shamu/shamu:6.0.1/MOB30I/2756745:user/release-keys
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc: 1/by-name/boot:8391910:043f426b9056cb46e8532a ..... has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
brucechidester said:
Verifying current system...
"EMMC:/dev/block/platform/msm_sdcc: 1/by-name/boot:8391910:043f426b9056cb46e8532a ..... has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation Aborted
Click to expand...
Click to collapse
It means you modified your system partition, so the OTA fails.
But it usually means your bootloader is unlocked so you should download the factory image, and flash the bootloader, radio, boot and system from the factory image, format the cache. Then you have your update.
You should flash the factory image, Google Nexus Factory Image and maybe look around if their explanation isn't enough for you on Google's page
Sent from my Nexus 6