If we thought the instructions for updating software on the A5 through the TF card reader was bad. Wait until you see the instructions for the newest mandatory hardware update PDF titled "Mandatory hardware fix to avoid overheating in A5 dashmaster". It's actually hilariously poorly written.

Any other legitimate company would offer a paid recall of their product and fix their overheating hardware issue to maintain their reputation and trust. I guess since it has been made clear that all their customers are dissatisfied and angry at Innosilicon, I guess they figure they have nothing to lose by issuing their latest update requiring the customers to do it themselves.

Apparently their warranty seal means nothing if they are demanding that customers actually open up their miners and fuck with very intricate components Not that it matters to me because mine came with broken warranty seals anyways

I'm surprised that my A5 is actually hashing nicely at 33 GH/s. Everything they do is such a facepalm that it seems like a miracle that they actually managed to create the worlds most efficient Dash miner (commercially available at the time of this post).

Also, changing topic, more A5's are popping up on eBay. The one I saw today was selling as a "Buy it now" / "Free shipping" for $5300 US... Ouch.

I also have some Innosilicon A5's I've been trying to get in Awesome Miner and was finally successful tonight. You need to edit three lines in the /home/inno_py/inno_config.py file. It looks like it generates a new run.sh file for each pool/pool change. I highlighted the lines and the adds below:

gInnoInitCmdStr = 'innominer_%s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 > /dev/null 2>&1'
gInnoBtcName    = 'T1'
gInnoBtcPool    = 'stratum+tcp://btc.s.innomining.com:1800'
gInnoBtcUser    = 'inno.btc'
gInnoBtcPwd     = 'x'
gInnoBtcFreq    = 1332
gInnoBtcVid     = 10
gInnoInitBtcCmd = gInnoInitCmdStr % (gInnoBtcName, gInnoBtcPool, gInnoBtcUser, gInnoBtcPwd, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcVid)
gInnoLtcName    = 'T2'
gInnoLtcPool    = 'stratum+tcp://ltc.s.innomining.com:1900'
gInnoLtcUser    = 'inno.ltc'
gInnoLtcPwd     = 'x'
gInnoLtcFreq    = 1044
gInnoLtcVid     = 25
gInnoInitLtcCmd = gInnoInitCmdStr % (gInnoLtcName, gInnoLtcPool, gInnoLtcUser, gInnoLtcPwd, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcVid)
gInnoDashName   = 'T3'
gInnoDashPool   = 'stratum+tcp://dash.s.innomining.com:2000'
gInnoDashUser   = 'inno.dash'
gInnoDashPwd    = 'x'
gInnoDashFreq   = 1100
gInnoDashVid    = 12
gInnoInitDashCmd= gInnoInitCmdStr % (gInnoDashName, gInnoDashPool, gInnoDashUser, gInnoDashPwd, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashVid)
gInnoXmrName    = 'T4'
gInnoXmrPool    = 'stratum+tcp://a8.s.innomining.com:19333'
gInnoXmrUser    = 'inno.001'
gInnoXmrPwd     = 'x'
gInnoXmrFreq    = 1000
gInnoXmrVid     = 175
gInnoInitXmrCmd = gInnoInitCmdStr % (gInnoXmrName, gInnoXmrPool, gInnoXmrUser, gInnoXmrPwd, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrVid)
gInnoCmd1Pool   = gInnoInitCmdStr
gInnoCmd2Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'
gInnoCmd3Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'

Yeah, that's right .sh. Good morning  

If your processes (ps) has  the flags in it then there might be something else wrong (not your config files)


https://i.imgur.com/yC9Qpxw.jpg
Shows the window in awesome when it works here. Manually typing address. Probably had to choose CgMiner from the drop-down the first time too.
Or you can try the network scan window thing, if you haven't.

What does worry a bit:
A) different miner, so who knows if any of this is helpful
B) if you have config *running* showing the --api-allow W:0/0 then there could be an entirely different set of problems like network connectivity issues. Firewalls. etc.

I have to wait till the miner is fully booted and mining before it will show in awesome. Once the webUI shows up it will show in awesome as well.
Uhm... also. your screenshot doesn't show a closing quote (& ') on that line. Probably just cut off by the view. just double check that too?

CAN WE CALL IT SCAM YETH???

En que mes recibiras los L3? puede que este interesado no lo se, porque el rendimiento que daria ahora mismo no sera el mismo que en unos meses