• We would like to remind our members that this is a privately owned, run and supported forum. You are here at the invitation and discretion of the owners. As such, rules and standards of conduct will be applied that help keep this forum functioning as the owners desire. These include, but are not limited to, removing content and even access to the forum.

    Please give yourself a refresher on the forum rules you agreed to follow when you signed up.

FW 2.0 beta 2 - rolling back kills Axe Fx II MK II

They would provide them for a small fee in the past. It couldn't hurt to contact support if you wanted to have one on hand. I've often considered it myself since I have an OCD that compels me to load each one, including the betas. Thankfully I've never had a problem to date.

Flash memory is actually a pretty flaky tech overall.
 
Can one buy the boot prom just to have in case ? I'm thinking it might be nice to have if a situation comes up when on the road. Support it super fast I'm sure but could be nice to have the means to solve the problem right after it happens.

I've always been aware of the risk for bricking my MkII... What I didn't know before reading this thread was that FAS will sell you an EEPROM which would mean the unit can be brought back to life without big delays and without the need to ship the whole unit in for service.

Thanx to the OP for sharing... Yes, support is the solution here but I found the info in this thread useful.

What's the cost of the EEPROM? I may look to get one on-hand just for a recovery option...
 
Corrupt downloads shouldn't be an issue. Fractal Bot checksums the file before transferring and then again after programming.

I think the primary issue is people shutting off the Axe when Bot says the transfer is complete and then ignoring/missing the part that says "wait until the front panel says to shut down before turning off the device."

When it happened the couple times with my XL/Fractal Bot, it was always during the actual transfer process of the FW proceeded by a, "transfer error" as per Bot's window/notification.

Prior to Fractal Bot there were no check sums with other transfer utilities other than the AFX II's display after the transfer completed, (check sum error)(if memory serves me correctly) as it was a few years ago now. Lets just say that with the Axe (gen.I), I had the manual ROM boot procedure down pat and left only 4 screws fastening the cover with it the Axe unracked. That's how frequent it happened and the main reason I got the XL. I tried troubleshooting as best as I knew how with the obvious, (usb cables, using different SysEx utilities, closing all programs other than what was needed for the transfer, etc.)... just like clockwork, every other or third FW update it would bork. I don't think we never got any resolve from Fractal about these isolated anomalies.

And I'm sure that in some cases you are right when people have shut their Axe off before the install of the FW procedure had been fully complete. If that be the case... hopefully they'll learn.
 
Last edited:
Just wanted to add that I rolled back my AxeFX II Mark 1 without any issue so I'm sure it doesn't matter which direction you go, it just so happened to be a bad upgrade.
 
When it happened the couple times with my XL/Fractal Bot, it was always during the actual transfer process of the FW proceeded by a, "transfer error" as per Bot's window/notification.

Prior to Fractal Bot there were no check sums with other transfer utilities other than the AFX II's display after the transfer completed, (check sum error)(if memory serves me correctly) as it was a few years ago now. Lets just say that with the Axe (gen.I), I had the manual ROM boot procedure down pat and left only 4 screws fastening the cover with it the Axe unracked. That's how frequent it happened and the main reason I got the XL. I tried troubleshooting as best as I knew how with the obvious, (usb cables, using different SysEx utilities, closing all programs other than what was needed for the transfer, etc.)... just like clockwork, every other or third FW update it would bork. I don't think we never got any resolve from Fractal about these isolated anomalies.

And I'm sure that in some cases you are right when people have shut their Axe off before the install of the FW procedure had been fully complete. If that be the case... hopefully they'll learn.

I wasn't trying to imply user error in all cases, so I apologize if it came across like that. As someone who has had several USB memory sticks fail on me, I know flash memory isn't super robust and reliable. But in my time here I think I've seen an almost equal number of "I shut the unit off before the update was complete", as the related "I don't know how I bricked it."
 
No need to apologize. I never thought you were implying that, "solely". No worries, man. I apologize if I caused you to think that in my reply.
I sometimes dislike text as it so often leads to misinterpretation. I was just recollecting to the best of my abilities as to what was going on in my particular circumstance(s). I'll often quote/reply to somewhat contain the sidebar conversations going on in the thread..It's all good. :D
 
Back
Top Bottom