Radio failed signature - Nexus One Q&A, Help & Troubleshooting

This what I get if I try to flash the latest radio in fastboot...
D:\AndroidSDK\android-sdk-windows\tools>fastboot flash radio radio.img
sending 'radio' (26112 KB)... OKAY [ 3.463s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
Can someone explain what i'm doing wrong here? Or maybe someone can make a signed zip, then I can just flash it in recovery?

Is your bootloader unlocked?

Rusty! said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, it's not. Is it necessary? And if I unlock it, will I loose any data/settings in my ROM?
EDIT:
Just unlocked the bootloader, it seems the ROM has been reset after doing this, but np
And radio flashed succesfully Thx!

Related

[Q] Signature failed in restore recovery

hi, i had the frf91 vodafone version on my nexus one. i thougth to install the frg83d posted here with rom manager. Everything went fine but the installation didn't restore the recovery and if i try to flash it with fastboot:
C:\android\tools>fastboot devices
HT05EP800252 fastboot
C:\android\tools>fastboot flash recovery recovery.img
sending 'recovery' (2294 KB)... OKAY [ 0.344s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.734s
am i doing something wrong?
is it because i'm rooted? i rooted my N1 without unlocking the bootloader.
Thanks
I dont think you can use fastboot to flash the recovery image without unlocking, you need to install the appropriate binary (/system/bin/flash_image) and call it from a shell on your phone (using a desktop is ok)
see http://forum.xda-developers.com/showthread.php?t=687280
http://www.droidforums.net/forum/dr...covery-framework-res-apk-custom-boot-ani.html
I would also say you lost root when updating your ROM. Also, you can't fastboot flash unofficial files without unlocking the bootloader.
Root, and flash through adb or ROM Manager, etc
Sent from my Nexus One using XDA App

[Q] How to update from FRG83G to GRI40 ?

I flash a FRG83G rom from http://forum.xda-developers.com/showthread.php?t=927935
Now I want to update to GRI40 using the following thread:
http://forum.xda-developers.com/showthread.php?t=968499
Unfortunately, when I want to flash HBoot 0.35.0017.
I meet trouble.
Code:
c:\fastboot flash hboot hboot.img
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
What should I do if I want to update to GRI40 ?
Flash through recovery.
I found the solution at http://forum.xda-developers.com/showthread.php?p=11624604#post11624604

[Q] Problem updating to GRI40 from FRF91

I have a rooted FRF91 install.
Tried installing the modified GRI40 version here:
http://forum.xda-developers.com/showthread.php?t=968396
I flashed to the Radio version with no problem, but I can't flash hboot.
I get the following msg:
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
Any ideas?
BTW: Can someone explain what is hboot exactly? couldn't find a decent explanation anywhere...
Flash it from recovery instead.
HBOOT is the bootloader, basically.

[Q] Not able to flash recovery.img after S-OFF and firmware upgrade

Hi,
I S-OFF'ed my HTC One, and upgraded the firmware!! Now i have a problem flashing the recovery.
When I'm trying to flash the recovery I'm only getting:
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.223s
Any idea of why its giving me remote: not allowed?
Have you tried to change the cable or the usb port?
However, all the other command will work?
Hehe never mind, it was a total brainfreeze, when i used revone, i also locked the bootloader again so unlocking it again kinda helped hehe
Thanks for the reply anyways

[Q] Latest Firmware Fails Fastboot

When I try to update my firmware to the 4.06.6514 firmware. I follow the directions in the thread, but when I issue the flashboot flash zip firmware.zip it fails with the following:
target reported max download size of 1526722560 bytes
sending 'zip' (20935 KB)...
OKAY [ 2.217s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 2.465s
The download seems OK, it passed the md5 check, etc... I haven't seen anyone else with this problem while looking around. Any ideas?
Thanks!
Did you update with the modified or unmodified firmware?
Sent from my HTCONE using xda app-developers app
o350125 said:
When I try to update my firmware to the 4.06.6514 firmware. I follow the directions in the thread, but when I issue the flashboot flash zip firmware.zip it fails with the following:
target reported max download size of 1526722560 bytes
sending 'zip' (20935 KB)...
OKAY [ 2.217s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 2.465s
The download seems OK, it passed the md5 check, etc... I haven't seen anyone else with this problem while looking around. Any ideas?
Thanks!
Click to expand...
Click to collapse
DID YOU TRY reentering the command : fastboot flash zip firmware.zip imediately after the error(works sometimes) did you rename the download zip to firmware/
I flashed the unmodified firmware for the 3.05 firmware with the 1.55 hboot and got a similar message. I just rebooted and everything was fine.
Sent from my HTCONE using xda app-developers app
Yeah we need some more info
S-ON or S-OFF?
Modified or unmodified firmware?
BD619 said:
Yeah we need some more info
S-ON or S-OFF?
Modified or unmodified firmware?
Click to expand...
Click to collapse
I was trying the unmodified firmware, and I believe that I AM S-ON, as I have never done anything special to get S-OFF.
I did try reissuing the command immediately after the fail a couple of times, and I did rename the firmware file as downloaded to firmware.zip
Thanks again!
o350125 said:
I was trying the unmodified firmware, and I believe that I AM S-ON, as I have never done anything special to get S-OFF.
I did try reissuing the command immediately after the fail a couple of times, and I did rename the firmware file as downloaded to firmware.zip
Thanks again!
Click to expand...
Click to collapse
Did you re-lock your bootloader?
BD619 said:
Did you re-lock your bootloader?
Click to expand...
Click to collapse
Is that something that you're supposed to do before updating? I'd never heard of that.
o350125 said:
Is that something that you're supposed to do before updating? I'd never heard of that.
Click to expand...
Click to collapse
yeah you have to relock your bootloader for the firmware to flash successfully. you can do this through the command "fastboot oem lock" in cmd that you opened in the same folder location as your fastboot binaries
BUT be careful because if you do this you will lose everything on your phone, including all of the stuff you have on your internal storage, etc. i just performed this operation yesterday and had gotten that same error before i re-locked
o350125 said:
Is that something that you're supposed to do before updating? I'd never heard of that.
Click to expand...
Click to collapse
If you are S-ON you do indeed have to re-lock your bootloader

Categories

Resources