search

GideonZ / 1541ultimate

Official GIT archive of 1541 ultimate II sources
GNU General Public License v3.0
178 stars 45 forks source link

Update from 3.7 to 3.10 bricked my Ultimate #254

Open Flexmaen opened 2 years ago

Flexmaen commented 2 years ago

I am using a C128 and had Firmware version 3.7 on my device (Ultimate 2). I tried to install 3.10 from there Now all I can do with this device is hitting the reset button - the other buttons don't show any reaction anymore. I also tried on a C64, but same problem there.

GerbilSoft commented 2 years ago

I had the same problem when updating to 3.10a dual-drive. There was a similar report here: https://github.com/markusC64/1541ultimate2/issues/31 - this issue has some suggested fixes using recover.u2u and ultimate.bin. Ultimate.bin (which should load the Ultimate application from SD instead of internal flash) didn't work for me at all; recover.u2u sometimes loaded the 3.10a updater, but it never ran successfully.

What ended up fixing it for me was running the 2.6k downgrader that was included with 3.0b7, then re-upgrading to 3.0b7, 3.0 final, and then 3.10a audio. (I think 3.10 dual-disk also worked, but not 3.10a dual-disk.)

I'd recommend trying the ultimate.bin method and recover.u2u using a recent version first, but if that doesn't work, use the 2.6k downgrader: https://github.com/GideonZ/ultimate_releases/raw/master/1541u2_3.0beta7.zip - copy revert.u2u to the SD card, renamed to recover.u2u, and boot the system.

Flexmaen commented 2 years ago

Oh, thank you very much! I could restore my Ultimate-II using the 2.6k downgrader. Then I went to 3.0b7 => 3.10 audio => 3.10a audio That also works on my C128!

MichaelHuth commented 2 years ago

Thanks for the hint to recover to the 2.6k version, which worked for me.

Then I tried upgrading towards 3.10 again, but it did not work out. Here is what I did:

After I recovered to the 2.6k I updated to the 3.0b7 which worked. Then I tried to update further to the 3.10a and I only see briefly the progress bar that the u2u image is loaded and then the 1541U2 freezes. After a power cycle I am back at 3.0b7.

So I though to upgrade stepwise and downloaded 3.2, 3.6 and 3.7 as well. 3.0b7 to 3.2 worked. 3.2 to 3.6 failed with the same "bricked" result as originally. Starting from 3.2 the u2u for 3.6 loads, I acknowledge the update process. It flashes until it asks for the configuration clear. I choose "yes" and after about one second it should reset and the retro replay screen should come up. But thats not what happens, instead it freezes, keyboard and buttons do no react. A power cycle leaves the 1541U2 in the "bricked state". Though reverting back to 2.6k and then going up to 3.2 worked and there I am stuck.

Flexmaen commented 2 years ago

@MichaelHuth from 3.0b7 i went to 3.10 and then 3.10a, that worked. I also used the audio-versions for 3.10 and 3.10a, didn't try the others.

Grrrolf commented 2 years ago

@Flexmaen, if your issue has been solved, can you please close the ticket?

Flexmaen commented 2 years ago

i could recover my device but i'm not sure if the issue itself is solved, if this is a problem of 3.7 or needs to be fixed in te 3.10 update.

MichaelHuth commented 2 years ago

So, I sent my 1542U2 to @markusC64 to reproduce the upgrade failing. But he could not reproduce it using a Ultimate 64 and on another attempt a breadbin C64.

On the other hand the flashing failed with using a Ultimate64 and my Breadbin C64 setup here.

Our current suspicion is that the problem is not the 1541U2 itself, but it is somehow related to the C64 where it is plugged or its power supply.

Flexmaen commented 2 years ago

I used a C128 DCR for the update.

GerbilSoft commented 2 years ago

I had also used a 128 DCR (NTSC) for the 3.10a-DualDrive update. I think I tried a C64C afterwards, but that might've just been to see if I could get it working in the "bricked" state, not trying to install 3.10a-DualDrive.

GerbilSoft commented 1 year ago

For what it's worth, I upgraded my 1541UII from 3.10a Audio to 3.10j Dual Drive today with no issues. I used an NTSC C64C to run the update.