You mean other than support???Yes , I did......I hoped someone has got the right idea.....
^^^thisYou mean other than support???
Good to make this known publicly if it's likely to happen to others
Yes shure.............seems like the Axe is without any programming.............so it don´t know what to do..............but there´s no "First Aid" - knob to lead it back to Axe Edit or Bot.You mean other than support???
And we can't, if people don't make it publicly known at all (and instead simply go direct to Support).But we don't know that. At all.
im sure if it was a more widespread issue it would be known and addressed by fractalAnd we can't, if people don't make it publicly known at all (and instead simply go direct to Support).
And we can't, if people don't make it publicly known at all (and instead simply go direct to Support).
This. You bricked your AFX. We can't do anything for you. As for it being some general thing, flashing a firmware is ALWAYS a chance to brick a device; this is why smartphones, laptops, etc, won't load an update unless the battery is at a certain percentage or plugged in, etc. Fortunately for XL series device owners, there is a hardware recovery method built into the device that is not affected by a flash... so they can recover from a bad flash via a special boot procedure but for Mki/II, however, there is always a risk that your device will be bricked when you flash (example power outage during the 'programming' phase of the flash).It's the symptoms of a bad flash. It's fixable but you'll need to get one of the boot proms and install it so you can boot into a recovery mode and re-flash. Support will get you straightened out.
They added the recovery prom to the XL & XL+ models, but the MK. II didn't have it built in.
When I had my AFX II MK I, it bricked on me quite a few times. I was using fast internet and a wired connection with nothing running as far as software goes. Just Fractal Bot or the the available sysEx. tools that were available before Bot. At any rate, I always suspected corrupt downloads. Something in the transfer while downloading as loading new FW was not a issue for 99.99% of other users.
Since I have had the XL it still happened a couple/few times. So what I always do is download the FW, (or whatever) two or three times and use the re-downloads if loading the new FW fails and trash the one that bricked.
I'm no computer ninja by any regard but I have had the same initial downloads re-brick while no issues with secondary downloads.
The best solution for that scenario (if corrupt downloads really were the issue) is to ask FAS to post MD5 hashes on their downloads page.