PDA

View Full Version : I think I bricked my TI Keyboard updating to 2.7.3


AtomX
04.09.2008, 03:20 AM
I just ran the update from 2.7.0.48 to 2.7.3.00 on osx 10.5.4

Everything seemed to go well, I ran updater it updated software, found my virus and updated the firmware ( was very quick, almost too quck) and then said that the system needed to restart. I noticed though at this point the virus was still showing in update mode on the LCD.

After the reboot of my PC the screen on the virus was still stuck on update and all controls on the virus did not function. I decided to run the Control center to see if the virus was detected still which it was and it said that it needed updating to the latest revision. It still detected it as 2.7.0.48 needing to go to 2.7.3.00. I let it complete the update, the progress bars on the virus screen and my computer all worked. It took maybe 10 minutes and then it said that it completed successfully and the virus needed to be rebooted. I thought that all was well but then after the reboot I observed in horror as the startup screen still said 2.7.0.48 and the unit went into a reboot loop. It gets to the end of the startup progress bar and at the end spontaniously reboots. I have tried leaving the power unplugged, factory reset using the hold arp edit button, this works, however the unit then still reboots at the end of startup.

I can only presume something bad has gone wrong and I have a bricked TI... Nightmare come true!

Can anyone suggest anything to try?
Will Access let me send it for repair if its older than 2 years?

thelike5
04.09.2008, 03:29 AM
I just ran the update from 2.7.0.48 to 2.7.3.00 on osx 10.5.4

Everything seemed to go well, I ran updater it updated software, found my virus and updated the firmware ( was very quick, almost too quck) and then said that the system needed to restart. I noticed though at this point the virus was still showing in update mode on the LCD.

After the reboot of my PC the screen on the virus was still stuck on update and all controls on the virus did not function. I decided to run the Control center to see if the virus was detected still which it was and it said that it needed updating to the latest revision. It still detected it as 2.7.0.48 needing to go to 2.7.3.00. I let it complete the update, the progress bars on the virus screen and my computer all worked. It took maybe 10 minutes and then it said that it completed successfully and the virus needed to be rebooted. I thought that all was well but then after the reboot I observed in horror as the startup screen still said 2.7.0.48 and the unit went into a reboot loop. It gets to the end of the startup progress bar and at the end spontaniously reboots. I have tried leaving the power unplugged, factory reset using the hold arp edit button, this works, however the unit then still reboots at the end of startup.

I can only presume something bad has gone wrong and I have a bricked TI... Nightmare come true!

Can anyone suggest anything to try?
Will Access let me send it for repair if its older than 2 years?

Hey AtomX,

Hold down the EXIT button while you power the Virus TI on.
This should manually boot your Virus in update mode, and you should be saved.

Please let me know if this works.

AtomX
04.09.2008, 05:21 AM
Sorted, thanks a million.

I was looking all over for a firmware recovery mode.
That did it, I dont know why the first time round it failed.

But it WORKS !!!

thelike5
04.09.2008, 05:31 PM
Sorted, thanks a million.

I was looking all over for a firmware recovery mode.
That did it, I dont know why the first time round it failed.

But it WORKS !!!

I'm fairly confident that the OS used inside of an Access Virus Synth is a very stable, flexible operating sysytem, not unlike those found in personal computers. There is usually always a way to recover from a crash... unless maybe it was do to a freak power surge (but I'm assuming you are protecting yourself with a real surge protector, not just a power strip right?)

You get what you pay for with Access. It would be a shame if a freak power outage or bad weather killed anybodys Virus.