Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

<remote signature verify fail> upon flashing radio in fastboot


  • Please log in to reply
9 replies to this topic

#1 polaris2k3

polaris2k3
  • Members
  • 19 posts
  • Country:
    ca - Canada
  • Device Model:
    N1
  • CM Version:
    CM7
  • Recovery Image:
    ClockworkMod

Posted 19 February 2011 - 12:10 PM

Hello! I recently rooted, installed ROM manager and flashed Clockworkmod on my N1 and installed CM7 RC1 (CM7 is completely awesome, btw). But I was using the old 4.06.00.12 radio, so I wanted to update to the newer 5.12.00.08 radio to see if it will fix the problem where my phone will get stuck on getting a 2G signal even when a strong 3G signal is available. I only rooted the phone, so my bootloader is still locked and I came from a stock 2.2.2 Google gave me OTA last month.

But when I tried to flash the radio with the .img in a zip file in clockworkmod recovery, it tells me the script has been disable (?). I got the radio image off the download section here on cyanogen, and the hash on the file is fine, so I dont know whats going on with it.

Then I tried to push the image to the phone via fastboot, using instructions found here: http://forum.xda-dev...ad.php?t=698721

But now it gives me this error:
"
    sending 'radio' (26112 KB)... OKAY [  3.844s]
               writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 6.797s
"

Anyone knows going on here and help me out? Thanks!!

Edited by polaris2k3, 20 February 2011 - 10:04 AM.


#2 polaris2k3

polaris2k3
  • Members
  • 19 posts
  • Country:
    ca - Canada
  • Device Model:
    N1
  • CM Version:
    CM7
  • Recovery Image:
    ClockworkMod

Posted 20 February 2011 - 05:59 AM

bump

#3 crawler9

crawler9
  • Members
  • 66 posts
  • Country:
    us - United States
  • Device Model:
    BLLockedLEDT-Mo N1
  • CM Version:
    Always Changing
  • Recovery Image:
    Amon_RA

Posted 20 February 2011 - 07:49 AM

Sounds like your bootloader is locked. You can't flash via fastboot if your bootloader is locked. You'll need to flash a radio through recovery.

#4 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 20 February 2011 - 07:57 AM

If you are running clockworkmod v3.* downgrade it to a 2.x version. There are some issues with some zips on cwm 3 (due to these scripts using a deprecated command that was removed out of v3).

#5 polaris2k3

polaris2k3
  • Members
  • 19 posts
  • Country:
    ca - Canada
  • Device Model:
    N1
  • CM Version:
    CM7
  • Recovery Image:
    ClockworkMod

Posted 20 February 2011 - 10:09 AM

View Postbassmadrigal, on 20 February 2011 - 07:57 AM, said:

If you are running clockworkmod v3.* downgrade it to a 2.x version. There are some issues with some zips on cwm 3 (due to these scripts using a deprecated command that was removed out of v3).

Ahhh, I see. So I couldn't use fastboot to flash cause my bootloader was still locked. And my CWM v3 doesnt support the scripts in the zip file.

So should I expect any trouble if i downgrade my cwm to a 2.x version, flash my radio, then boot back into CM7 to use ROM Manager to upgrade my cwm back into 3.0.0.5? Or would I not be able to boot back into gingerbread after going back to a cwm 2.x?

#6 temasek

temasek
  • Donators
  • 3345 posts
  • Twitter:temasek71
  • Country:
    sg - Singapore
  • Device Model:
    Nexus One / O2X
  • CM Version:
    CM7.2.0 RC0 SelfKANG
  • Recovery Image:
    Amon_RA

Posted 20 February 2011 - 10:40 AM

Downgrade to CW2.xx, flash radio. Don't upgrade back to CW3+

#7 polaris2k3

polaris2k3
  • Members
  • 19 posts
  • Country:
    ca - Canada
  • Device Model:
    N1
  • CM Version:
    CM7
  • Recovery Image:
    ClockworkMod

Posted 20 February 2011 - 10:58 AM

hmm..but why not?

#8 temasek

temasek
  • Donators
  • 3345 posts
  • Twitter:temasek71
  • Country:
    sg - Singapore
  • Device Model:
    Nexus One / O2X
  • CM Version:
    CM7.2.0 RC0 SelfKANG
  • Recovery Image:
    Amon_RA

Posted 20 February 2011 - 11:08 AM

Nvm......upgrade back if u wish.

#9 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 20 February 2011 - 02:49 PM

View Postpolaris2k3, on 20 February 2011 - 10:58 AM, said:

hmm..but why not?

With v3* they took out the "update" command (at least, that is what I think it is). This command was deprecated by google quite a while ago and replaced with the edify command. Unfortunately, people still continued using the update command even though they weren't supposed to. So when support for update was dropped in v3, many flashable zips fail (or cause issues), because of this.

However, v2 supports both (at least, I think they do, I haven't done too much research) commands, and most zips were written with v2 in mind. There may also be some bugs with v3 that may be causing additional problems (but I haven't heard anything definitive on this).

Basically, v2 is still more compatible than v3.

#10 polaris2k3

polaris2k3
  • Members
  • 19 posts
  • Country:
    ca - Canada
  • Device Model:
    N1
  • CM Version:
    CM7
  • Recovery Image:
    ClockworkMod

Posted 20 February 2011 - 04:22 PM

I see..thanks for the help guys! I downgraded back to v2 and then flashed the radio. Will have to try it over the next few days to see if it made a difference. Can't wait till CM7 final comes out though!