frg22 e:signature verification failed

Discussion in 'Motorola Droid' started by rcbjr2, Aug 5, 2010.

  1. rcbjr2
    Offline

    rcbjr2 New Member

    Joined:
    Aug 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    I manually updated my droid with the frg01b(?) build this a.m. My droid 1 is not rooted. This worked just fine. However, when I now try frg22, I get the frg22 e:signature verification failed error and it won't update. I followed all of the usual instructions (e.g., renaming file to update.zip, putting it in root folder, etc.) (and it worked for frg01b(?) so I did the same thing for frg22). Should I have gone straight to frg22 from 2.1? Would that have worked? Shouldn't frg22 install over frg01b?? How can I get rid of the "signature verification failed" error??

    Thx.

    -Rich
  2. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    I had the same error on my unrooted Droid 1. In order to install FRG22 I'm pretty sure you have to be using SPRecovery since it isn't a "signed" release.

    I used these instructions just using the FRG22 file in place of "a 2.1 rooted ROM" and that worked fine.

    Hope that helps.
  3. rcbjr2
    Offline

    rcbjr2 New Member

    Joined:
    Aug 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    Thanks. I will try that. I don't really want to root the phone, but in reading the instructions, it looks like install a couple of applications and then instead of doing a rooted 2.1 install, I just substitute frg2.2 instead. This is a bit more complicated than I can accomplish here at the office because several of the sites where I need to download apps are blocked. ;-) I'll have to try it this weekend at home.

    Thx.
  4. mcapozzi
    Offline

    mcapozzi New Member

    Joined:
    May 21, 2010
    Messages:
    272
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Liverpool, NY
    I think you would have to root your FRG01 install first.

    -Mike
  5. rcbjr2
    Offline

    rcbjr2 New Member

    Joined:
    Aug 5, 2010
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    0
    I think you might be right. At least all the posts I see for FRG22 call it the "root" version. Oh well. Not sure I want to do that, but we'll see. I'd love to have Titanium Backup running, though. As much as I mess with the Droid, though, not sure I have even more time to download special ROMs, etc. ;-)

    Thx.

    -Rich
  6. MotoCache1
    Offline

    MotoCache1 Chief Droid Scientist

    Joined:
    Jun 30, 2010
    Messages:
    530
    Likes Received:
    1
    Trophy Points:
    0
    I didn't. I started with an original, stock, non-rooted 2.1, and then flashed on SPRecovery and then used SPRecovery to put the rooted FRG22 on. Heck, I even (accidentally) skipped the "Wipe cache partition" step and it still went fine. No odd results yet. Still haven't found anybody who knows (or has replied and said) what potential problems I should expect from not wiping anything before going straight from stock, non-rooted 2.1 to rooted FRG22.
  7. hookbill
    Offline

    hookbill Premium Member Premium Member

    Joined:
    Nov 30, 2009
    Messages:
    19,545
    Likes Received:
    5
    Trophy Points:
    0
    Location:
    N.E. Ohio
    Let me try to clear this up. With the first Froyo came an update that you could use that was not rooted. However every other update since then comes with a root. That means that when you rename the file to update.exe SPRecovery will install the update AND root your Droid.

    Let me know if you have other questions. I think this is where the misunderstanding is.
Search tags for this page
can i verify roms signatures so i dont get error signature v
,
e /signature 20verification 20failed
,
e signature%20verification%20failed
,
e:/%20signature%20verification%20failed
,

e:/signature%20verification%20failed

,
e:/signature%20verification%20failed%209.8.2o
,
e:/signature%20verification%20failed%20installtion%20aborted
,
e:%20failed%20to%20verify%20whole-file%20signature
,

e:signature verification failed

,
e:signature%20verification%20failed
,
e:signature%20verification%20failed%20galaxy%20vibrant
,
erore e:/signature%20verification%20failed
,
file:/e:/signature%20verification%20failed
,
google:e:/signature%20verification%20faild
,
signature 20verification 20failed