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
Related
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.
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...
Hello, I bought a unlocked&rooted nexus one with android 2.2 froyo
I'm new here but searched around to get a clear answer to this question, but was unable to due to overload of fragmented info:
Is it in any way possible or is there an easy way to let an automatically received (2-part) OTA update install on my rooted nexus froyo, with fastboot, hboot, clockworkmod?
If yes, how? because now i receive a 'E:No signature E:Verification failed' error when it's rebooting during the install process.
Is this because of the clockworkmod or what (if so, is it uninstallable..) ?
If not, what's the minimum I have to do to make the OTA update automatic install possible again ?
Many thanks & I'm very sorry if this Q has been answered a million times (in a fragmented way or not), but I just couldn't find it...
pipperss said:
Hello, I bought a unlocked&rooted nexus one with android 2.2 froyo
I'm new here but searched around to get a clear answer to this question, but was unable to due to overload of fragmented info:
Is it in any way possible or is there an easy way to let an automatically received (2-part) OTA update install on my rooted nexus froyo, with fastboot, hboot, clockworkmod?
If yes, how? because now i receive a 'E:No signature E:Verification failed' error when it's rebooting during the install process.
Is this because of the clockworkmod or what (if so, is it uninstallable..) ?
If not, what's the minimum I have to do to make the OTA update automatic install possible again ?
Many thanks & I'm very sorry if this Q has been answered a million times (in a fragmented way or not), but I just couldn't find it...
Click to expand...
Click to collapse
If you want to flash Google updates with a custom recovery like ClockworkMod, you need to disable signature verification...
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!
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