Author

Topic: How to bypass ""Cannot find Signature" when updating your antminer firmware. (Read 2266 times)

newbie
Activity: 2
Merit: 0
I used this method on a used L3+ I just got off eBay.  Great instructions, thanks for laying it out.

I'm having the same issues but it's not working for me. Can you help me with one? Happy to help out wherever I can (e.g. free Blissz software for anyone or other items).
copper member
Activity: 33
Merit: 0
I have a L3++ that has the signature not found issue. It is the most recent firmware from bitmain as of today, so it blocks the SSH. I am ready to do the SD card option but can not find the instructions or the download for it. Any help would be appreciated.
member
Activity: 125
Merit: 10
Years later, this topic helped me! Thanks!
SSH and vi needed to be able to update L3+ to nicehash firmware
newbie
Activity: 1
Merit: 0
no more possible to install blissz firmware on a updated l3+ july 2019 firmware.. , System Upgrade Failed - Cannot Find Signature!!! no putty ssh no more Huh
sr. member
Activity: 708
Merit: 250
Does that method work with the end of july firmware for S9 ?

Thx.
newbie
Activity: 328
Merit: 0
SD based install. instructions linked from https://releases.broked.net

-j

Ok I'll go to bestbuy and get a SD card but if this doesn't work Im warning you in advance I will drop one.
member
Activity: 504
Merit: 51
SD based install. instructions linked from https://releases.broked.net

-j
newbie
Activity: 328
Merit: 0
Thanks for info, but i can't get it working, my l3+ is on firmware 2018. After i followed your instruction and save the upgrade.cgi,

I try to upgrade it to the bliszz firmware, but the same cannot find signature error happened.

I need a firmware update for Z9 mini back to stock with frequencies unlocked this is annoying putty doesn't work for me I don't know what you are talking about how about a file that works I keep being victims to these people on ebay selling a fix that doesn't work I need something that works it was working fine then a pool keep reseting and my fan was waking me up so I thought I would upgrade the firmware sure enough  installed a asshole that puts " Balance " there and annoys people.  Grow up bitmain?  Grow up ebay?  Send me a file that works not sabatoges me and stabs me in the back.  ha ha ha ha I thought that was a japanese trait.
newbie
Activity: 1
Merit: 0
Thanks for info, but i can't get it working, my l3+ is on firmware 2018. After i followed your instruction and save the upgrade.cgi,

I try to upgrade it to the bliszz firmware, but the same cannot find signature error happened.
jr. member
Activity: 188
Merit: 2
In Blockchain we trust!
Have all kind firmwares to s9,t9,d3,l3 - pm me if you need. also can help with unlocking bitmains firmware
newbie
Activity: 2
Merit: 0
Where can you get original v1.0.1.3 for L3+, since it's not on the Bitmain website? The two links they have up are only for 1.0.1.4, which contain the "Cannot find Signature" issue, as well as no SSH.
I wanted to be able to go back and forth from Blissz to original Bitmain firmware, if need be.
newbie
Activity: 7
Merit: 0
Hi guys.

I cant acces ssh
 Connection failed. FlowSocketConnector: Failed to connect to target address. Windows error 10061: No connection could be made because the target machine actively refused it.
Is there any chance I can acces my L3+.

newbie
Activity: 3
Merit: 0
awesome the upgrade did take No more cannot find signature!! thanks
newbie
Activity: 3
Merit: 0
step 10
:q enter  then this shows up " -sh: :q: not found" does this look correct?   
newbie
Activity: 3
Merit: 0
i have a antminer L3+ when i upgrade to Blissz new firmware a pop up (cannot find signature) so i google it and found your post great step by step by the way, but for some reason it don"t work for me. wondering if it can be done on my miner. thanks
newbie
Activity: 4
Merit: 1
This worked for my L3+ that was on the blissz FW then downgraded to the L3++ FW from Bitmain, then back to Blissz.  After downgrading to L3++ I got the signature not found and did the above to fix.

Thank you!

Glad this worked out for you as well, did you face any difficulties? was the guide easy enough to follow? please let me know if you think i need to clear out any of the steps.

Thanks.

What if you can't SH in? Am I hosed?
member
Activity: 504
Merit: 51
I started to get this error after installing the new firmware of D3 so I did exactly the same Mike showed me how to.But Didn't work! then I realized in the www/pages/cgi-bin there is 3 file connecting each other and this three are calling each other.

"upgrade.cgi"
"upgrade_clear.cgi"
"upload_conf.cgi"

so I edited with this files in ssh editor I searched in existing "Cannot Find Signature" so I put # type before words as like Mike's codes. and worked for me. Thank you again Mike. Yes I think with the latest firmware having strong security with this 3 files I think.

There is a much much simpler way to do this.

mv /usr/bin/openssl /usr/bin/openssl.orig
echo > /usr/bin/openssl <#!/bin/sh
return 1
!
chmod +x /usr/bin/openssl

Done. Fixed. /usr/bin/openssl will return true, the "check" will pass... the only caveat is sometimes the firmware you want to upgrade to will need a 0 byte .signature file to pass the "-f" exists check.

-j
member
Activity: 133
Merit: 15
~ Fortuna Favet Fortibus ~
I started to get this error after installing the new firmware of D3 so I did exactly the same Mike showed me how to.But Didn't work! then I realized in the www/pages/cgi-bin there is 3 file connecting each other and this three are calling each other.

"upgrade.cgi"
"upgrade_clear.cgi"
"upload_conf.cgi"

so I edited with this files in ssh editor I searched in existing "Cannot Find Signature" so I put # type before words as like Mike's codes. and worked for me. Thank you again Mike. Yes I think with the latest firmware having strong security with this 3 files I think.
jr. member
Activity: 393
Merit: 1
Coinsbit exchange
ya apparently , i was not aware of this when i posted my last message, this method is useless if you have no access via SSH, all new 2019 firmware have the SSH function disabled, the only way to get around this so far is by using an SD card to flash your firmware.
It is a pity that there are no other options to solve this problem. This complicates the process a bit. But I hope that some solution will appear soon.
legendary
Activity: 2268
Merit: 6424
be constructive or S.T.F.U
Does that firmware also disable ssh? That's their new method, signature + disabling SSH.

ya apparently , i was not aware of this when i posted my last message, this method is useless if you have no access via SSH, all new 2019 firmware have the SSH function disabled, the only way to get around this so far is by using an SD card to flash your firmware.
member
Activity: 504
Merit: 51
update:

The new 2019 firmware for S9 also has this Signature restriction.

reference:

https://bitcointalksearch.org/topic/m.50535225



Does that firmware also disable ssh? That's their new method, signature + disabling SSH.

-j
legendary
Activity: 2268
Merit: 6424
be constructive or S.T.F.U
update:

The new 2019 firmware for S9 also has this Signature restriction.

reference:

https://bitcointalksearch.org/topic/m.50535225

legendary
Activity: 2268
Merit: 6424
be constructive or S.T.F.U
I used this method on a used L3+ I just got off eBay.  Great instructions, thanks for laying it out.

did you face any troubles along the way? glad it worked out for you.
jr. member
Activity: 51
Merit: 1
I used this method on a used L3+ I just got off eBay.  Great instructions, thanks for laying it out.
member
Activity: 504
Merit: 51
Hi, everybody. And that to do if I have on all miners z9 closed all ports except 4028? Huh

Your miner is showing the “November” build I guess. Use the sdcard recovery steps (google it) and then install a non locked firmware of your choice, mine from my signature or someone else's, as the last step (step #10 - unnumbered on the page below).

documentation: https://support.bitmain.com/hc/en-us/articles/360006020914-Z9-V9-Z9-Mini-Control-Board-Program-Recovery



-j

THX, Everything turned out as you said.

Awesome, I'm glad this worked out. I went ahead and created two boot images, one for the mini and one for the large which can be used to install Fuddware 2.1d in the future -- skipping the V9->upgrade step. It's now posted at https://releases.broked.net and can be used in place of the V9/Z9/Z9miniv2 images listed at bitmain's website.

-j
newbie
Activity: 2
Merit: 0
Hi, everybody. And that to do if I have on all miners z9 closed all ports except 4028? Huh

Your miner is showing the “November” build I guess. Use the sdcard recovery steps (google it) and then install a non locked firmware of your choice, mine from my signature or someone else's, as the last step (step #10 - unnumbered on the page below).

documentation: https://support.bitmain.com/hc/en-us/articles/360006020914-Z9-V9-Z9-Mini-Control-Board-Program-Recovery



-j

THX, Everything turned out as you said.
member
Activity: 504
Merit: 51
Hi, everybody. And that to do if I have on all miners z9 closed all ports except 4028? Huh

Your miner is showing the “November” build I guess. Use the sdcard recovery steps (google it) and then install a non locked firmware of your choice, mine from my signature or someone else's, as the last step (step #10 - unnumbered on the page below).

documentation: https://support.bitmain.com/hc/en-us/articles/360006020914-Z9-V9-Z9-Mini-Control-Board-Program-Recovery



-j
newbie
Activity: 2
Merit: 0
Hi, everybody. And that to do if I have on all miners z9 closed all ports except 4028? Huh
jr. member
Activity: 559
Merit: 4
LOL... OR, just follow the standard bitmain recovery instructions, but load the firmware of your choice instead of theirs as the last step.

I've already gone though and checked the various bitmain loader images a couple of days ago to make sure they do not have signature checking in them instead of making one-off images for a bunch of things.

-j



True, you can just follow the Bitmain recovery until they update the recovery image on their site. I had this one already put together for a guy.
member
Activity: 504
Merit: 51
LOL... OR, just follow the standard bitmain recovery instructions, but load the firmware of your choice instead of theirs as the last step.

I've already gone though and checked the various bitmain loader images a couple of days ago to make sure they do not have signature checking in them instead of making one-off images for a bunch of things.

-j

jr. member
Activity: 559
Merit: 4
For the ANtminer D3 I have created a SD loader for the Blissz v1.1 Dev-Free. This will load Blissz firmware and get rid of the signature checking. If you have other miners you need a similar files for pm me and I will see what I can get together for you to get past the SSH disable and Signature checking.

How to use.....

1) Unpack the files to a SD-Card
2) Power off miner
3) Insert SD-Card into miners SD Slot
4) Power miner back on
5) Wait about 3-5 minutes for the miner to boot and load Blissz v1.1 to the miner
6) Power off miner and remove the SD-Card
7) Power miner back on and enjoy Blissz v1.1 Dev-Free

You can download the Antminer D3 file here:

https://drive.google.com/file/d/1xVhPqAsRz3SW2kmWFEKdV8CuIYQkuglO/view?usp=sharing


If you find this file helpful please make a donation to my Dash wallet -     Xrf1K1vDwY9RoqrEJGABJMR8sbDHtWaxQy
or if you prefer Zcash -   t1e4Dmr5RBgnWqTN2mAmZ6JzGavW7qxA4P1

newbie
Activity: 29
Merit: 4
forgot to write to press esc after modification.......save with :wq does not works

legendary
Activity: 2268
Merit: 6424
be constructive or S.T.F.U
This worked for my L3+ that was on the blissz FW then downgraded to the L3++ FW from Bitmain, then back to Blissz.  After downgrading to L3++ I got the signature not found and did the above to fix.

Thank you!

Glad this worked out for you as well, did you face any difficulties? was the guide easy enough to follow? please let me know if you think i need to clear out any of the steps.

Thanks.
member
Activity: 504
Merit: 51
The only available L3+ firmware on Bitmain's site is: Antminer-L3+-201811131346-384M.tar.gz
If you update to it it adds the "Cannot find Signature" so no going back or going to Bliss.

I suspect that any Bitmain firmware for any miner from Nov/Dec 18 that says "Security Firmware, Fix some security vulnerabilities"
blocks unauthorized firmware, and rolling back to previous firmware.
Even resetting does not get around it.
 
Thanks for this work around.   

-M

bitmange is getting trickier in that they are also disabling SSH in their latest firmwares....

-j
full member
Activity: 159
Merit: 108
The only available L3+ firmware on Bitmain's site is: Antminer-L3+-201811131346-384M.tar.gz
If you update to it it adds the "Cannot find Signature" so no going back or going to Bliss.

I suspect that any Bitmain firmware for any miner from Nov/Dec 18 that says "Security Firmware, Fix some security vulnerabilities"
blocks unauthorized firmware, and rolling back to previous firmware.
Even resetting does not get around it.
 
Thanks for this work around.   

-M
newbie
Activity: 3
Merit: 0
This worked for my L3+ that was on the blissz FW then downgraded to the L3++ FW from Bitmain, then back to Blissz.  After downgrading to L3++ I got the signature not found and did the above to fix.

Thank you!
legendary
Activity: 2268
Merit: 6424
be constructive or S.T.F.U
mikeywith - do you know which miners are doing this now?

I'd be tempted to release a version of each that doesn't have this crap in it -- it's a ridiculously stupid check they've implemented. Their software prowess is sad.

-j

the once i am aware of are the D3 and the L3 as well as the L3++. but if i am not mistaken i have read someone had a problem with his S9 when trying to flush Briiins fw.

i hope other members will confirm about other miners.

the strange thing is even in D3 and L3, not all batches have this stupid signature check.
legendary
Activity: 2436
Merit: 1706
Electrical engineer. Mining since 2014.
Nice digging. Smiley

That's a quite simple if-function they have there for the signature check.
member
Activity: 504
Merit: 51
mikeywith - do you know which miners are doing this now?

I'd be tempted to release a version of each that doesn't have this crap in it -- it's a ridiculously stupid check they've implemented. Their software prowess is sad.

-j
legendary
Activity: 2268
Merit: 6424
be constructive or S.T.F.U
A few days ago, one member on forum asked how to bypass the ""Cannot find Signature" as he was trying to update his D3 miner, while this still applies to BTC miners too, so i decied to make this topic on this board, if the mods feel like it belongs to alts, please move it.


the initial thread to the guy's question can be found here > https://bitcointalksearch.org/topic/cannot-find-signature-whats-this-5088793

i gave him the soluation in step-by-step manner, so it's kinda hard to follow the whole process frorm the topic, as there were a couple of different posts, so what i am going to do here is basically combine the whole steps into 1 to make it easier to follow, if you want to check how did that guy do it and what difficulites he faced you can refer to the topic, also i would like to acknowledge that i used this russian website to learn about this method and it's only fair to post the link even if you can't read russian , i still feel the need for giving credit to the author.

https://forum.bits.media/index.php?/topic/65678-%D1%81%D1%82%D0%BE%D1%80%D0%BE%D0%BD%D0%BD%D1%8F%D1%8F-%D0%BF%D1%80%D0%BE%D1%88%D0%B8%D0%B2%D0%BA%D0%B0-%D0%B4%D0%BB%D1%8F-antminer-l3-%D0%BE%D1%82-blissz/&page=5&tab=comments#comment-1703686

 -------------------------------------------------------

lets start.

1- you will need to use a ssh tool like putty.

2-type the ip address of the miner in putty , keep port 22

* if message pop up > click Yes

3-username :root
  password:admin

then you will be inside the miner.

4-copy paste this line

Code:
cd /www/pages/cgi-bin
    > hit enter

like this



5-type this

Code:
vi upgrade.cgi


6-use the down arrow and find this code

-------------------------

Code:
if [ ! -f runme.sh.sig ]; then
        echo "Cannot Find Signature!!!" >> /tmp/upgrade_result
else
        openssl dgst -sha256 -verify /etc/bitmain-pub.pem -signature  runme.sh.sig  runme.sh >/dev/null  2>&1
        res=$?
        if [ $res -eq 1 ]; then
                echo "Installer Not Signtured!!!" >> /tmp/upgrade_result
        else
                if [ -f runme.sh ]; then
                        sh runme.sh
                else
                        echo "Incorrect firmware!!!!" >> /tmp/upgrade_result
                fi
        fi
fi

#if [ -f runme.sh ]; then
#       sh runme.sh
#else
#       echo "Incorrect firmware!!!!" >> /tmp/upgrade_result
#fi



7-click "i" on your keyboard to enter Edit Mode

8- change the code in step 6 to this code

" you don't have to delete or add any code, reffer to the comment below the code to understand more.

Code:
# if [ ! -f runme.sh.sig ]; then
      #  echo "Cannot Find Signature!!!" >> /tmp/upgrade_result
#else
 #  openssl dgst -sha256 -verify /etc/bitmain-pub.pem -signature  runme.sh.sig  runme.sh >/dev/null  2>&1
# res=$?
# if [ $res -eq 1 ]; then
 #   echo "Installer Not Signtured!!!" >> /tmp/upgrade_result
 #else
#    if [ -f runme.sh ]; then
#   sh runme.sh
 # else
# echo "Incorrect firmware!!!!" >> /tmp/upgrade_result
# fi
 # fi
#fi

if [ -f runme.sh ]; then
   sh runme.sh
else
       echo "Incorrect firmware!!!!" >> /tmp/upgrade_result
fi


"add # to the first 15 lines, and remove # from the next 5 lines"

* adding # meaning the line is commented aka won't be executed, so what you doing is simply making the miner ignore that IF function that looks for the signature.

after you are done editing the code, hit ESC key (escape) on your keyboard

9-type

Code:
:wq

and hit Enter > this code is to save and exist the upgrate file.

10-type
Code:
:q

and hit Enter > to exist the SSH session.

11-flush the new firmware.


------------------------------------
*do this at your own risk

if you have any questions feel free to ask.

Good luck.
Jump to: