rss

How to Bypass Android No Signature, Verification Failed Error

Author: Ben Johnson on October 9, 2010

Yesterday i received Android 2.2.1 (FRG83) update (signed-passion-FRG83-from-FRF91.c8847c98.zip) on my Nexus One OTA. Before applying the update, my Nexus One was running Android 2.2 (FRF91) which was rooted using 1-click Universal Androot utility. Only applying the update via stock Android system recovery, i got "No Signature, Verification Failed Error" error.

After installing Amon_Ra's Recovery image and downloading the (FRG83) update manually, i tried to install the update.zip via Amon_Ra's Recovery but unfortunately again got the same "No Signature, Verification Failed Error" error.

Android System Recovery Utility*Above image is for illustration purpose only

Finding update package...
Opening update package...
Verifying update package...
E:No signature (188 files)
E:Verification failed
Installation aborted.

To bypass this "No Signature, Verification Failed Error", you must install ClockworkMod Recovery image.

  • Start your Android phone normally and place update.zip in the root of your SD card.
  • Go to Android Market, search for ClockworkMod, select ROM Manager from the list and install it.
  • Once you have installed the ROM Manager, launch ROM Manager and grant Superuser Permissions to it.
  • Click on Flash ClockworkMod Recovery to install ClockworkMod Recovery image.
  • Choose Reboot into Recovery and ROM Manager will boot you to recovery mode.

    • ClockworkMod Recovery

  • If you'll apply update directly, you'll end up in the following error:

    • E:Error in /sdcard/update.zip
    (Status 7)
    Installation aborted

  • So choose "install zip from sdcard" option.

    • Toggle Signature Verification

  • Now first choose "toggle signature verification" to turn off the signature check and then choose "apply sdcard:update.zip".
  • Now you'll not see any errors related to signature and you can easily update your software.

*Note that this trick worked when i was updating Nexus One from Android 2.2 to Android 2.2.1 on an unlocked bootloader. It may or may not work with the other versions. So if you test it and find it working on any other version, please do mention the update in comments.



  • Hemant Anpat

    unfortunetly error in Android

  • defy fan

    Shashank,

    you need to come on the XDA defy thread or the TBHP android thread. Why do you need to bother with "apply update.zip" process when the "install from zip file" works without the signature verification nicely?

  • shashank Chauhan

    tried on defy motorola nothing happens same problem signature issue guess i have to stay on 2.2 :(

  • Jon

    Hey guys on my Droid 3 im trying to root it to get wifi to my xbox since we have no power at my house. i got my root234.zip in my SD card and everything is good until i try to run it. it says e:signature no granted or something like that and the installation is aborted. when i download this ROM Manager it gives me an error message
    "You must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use google search on your computer to find instructions on how to root your phone."

    Well im trying to do that but i need this E:signature to be toggled off and i thought this app could do that.

    How do i turn this off so i can root my phone? (Droid 3 - 2.3.4)

    Thanks for your hel;p

  • Mark

    Im having a problem: When i try to reboot in the clockworkmod recovery screen, i end up at the Android recovery screen with the yellow triangle with exclamation point and a small picture of my phone next to it please help

  • hunter

    i did this but i dont do anything except reboot i get no menu on anything, im on the latest software and my phone is flashed

  • Siddarth

    It worked on my HTC Wildfire! Thanks a lot

  • gogo

    I have a same problem as Sam. HTC Tattoo.

    Help anyone???

  • sam

    hi!

    first of all thanks for this guide that you provided! ok now for the question. i have a motorola milestone already rooted using universal androot.also already downloaded and installed the clockwork.I followed the instructions in your guide but when i choose "reboot into recovery" it just reboots to the android recovery not the clockworkmod recovery....if you can help me solve this problem it would help me a lot...thanks!!!

  • Carlos

    With my Galaxy S Froyo updated (2.2) and Vodafone locked, the app tell me that phone must be rooted? How I can use it for rooting?
    Thanks

  • R JaY

    I got same problem like jay.. i do what u said, all the steps you said. But still no where?

    when im done with all the steps it still says finding update package and then verification faild. i have toggle signature verification enbaled:S

    pleaaaseHELP

  • Jay

    I tried the instructions above, changed rom's zip file name to update.zip, disabled signature verification, chose apply sdcard:update.zip instead of choosing zip from sdcard but still got the status 7 error. I have clockworkMod v2.5.0.7

    Hope to have this issue resolved.

    Happy New Year guys!

    • marco

      Hi Jay,
      hope you have already resolved, some days have passed .. but in case you haven't: what do you mean with erro / still a problem of signature verification notwithstanding the fact you disabled it ?

  • Luis Martinez

    just did this to the moto cliq im stuck at the stick together screen! please does anyone know how to fix this????? i flashed 2.1 via clockwork need to know ASAP!

    • marco

      Luis I do not know what to tell you. I updated FROM 2.2 TO 2.2.1 on my N1 without any trouble following the instructions above. Running clockwork, then moving to install from SD, switching off the signature verification and then going with the FRG83_stock.zip: the entire ROM.
      Now, I can't update OTA (I couldn't even before , all in all) but my installation ran smoothly.

  • http://facebook.com/tenae Tenae

    You're awesome!!! Worked perfectly for my Motorola Cliq! I had to update to .5 to get to 2.1...it's been nightmarish and this worked just perfectly! THANK YOU!

  • kostah

    this was my key to FINALLY get rid of my vodafone branding on my nexus..
    BUT: when installing clockworkmod recovery, need to immediately go from it's menu to the recovery..otherwise during boot the branded rom wipes out the clockwork recovery.....if you normally quit clockwork after installation and shutdown phone, start in recovery, you will end up in default android system recovery , not the clockwork recovery you just installed..

    after installing a stock rom though, the CW recovery will survive :)

  • marco

    believe it or not, yesterday night I found the solution ... at least for me.
    I discovered that the problem was in the fact that I transferred the file FRG83_stock.zip (that is, the entire ROM including the 2.2.1 update) on the phone using a MAC. I do not know why, but when I did the same using WIN XP anything like smoothly, and now I'm updated to 2.2.1.

  • marco

    same to me, eyal. If I remove the signature verification the phone replies with error 7 installation aborted (erors in sdcard/update.zip something ...
    I searched for two days on the net, flashed rom in any way, formatted sd, changed sd, step back to eclair, forward to froyo, everything and anything. No way to overtake the problem. I surrended by now and wait for 2.3 to be released

  • Eyal

    I've tried your method step by step but I'm still getting Status 7 even after confirming I've toggled Signature Check. It looks like it's aborting during Verifying current system...

    I'm on Nexus One running FRF91.

    Any advice?

    Thank you.

  • Amon_RA

    Official OTA updates should only be flashed on official non rooted firmwares via stock recovery!

    An official OTA update assumes you have a stock ROM!

    Following the above method on a custom ROM (or an altered rooted stock ROM) WILL corrupt your system!!

    • http://jaxov.com/ Wolverine

      I actually tried it on my Nexus One already rooted on Android 2.2, it worked. Now i am running rooted Android 2.2.1 on my Nexus One.

  • ramadan

    I advise you not to do this if you have a nexus one. Mine just got fried! the screen is hung up on the unlocked image. (unlocked at the bottom and the four colored "x" above it). Any assistance on how to unfreeze my screen is greatly appreciated.

    • http://jaxov.com/ Wolverine

      Above procedure is completely safe, it'll never brick your device until your phone looses the battery power during recovery image installation. Press the Power and Trackball button at the same time to load the bootloader. Or use adb reboot bootloader at command prompt to load the bootloader directly.