danielkraak / GC-Loader

151 stars 9 forks source link

Error after update to FW 2.0.0 (not beta) #32

Open isynx opened 1 year ago

isynx commented 1 year ago

Today I updated the FW from 2.0.0 beta to 2.0.0 but then got error after rebooting saying: An error has occured.

Turn the power OFF and check the NINTENDO GAMECUBE Instruction Booklet for further instructions.

dejones972 commented 1 year ago

i have the same problem.

isynx commented 1 year ago

I wonder is there any way to downgrade easily as I already removed the optical drive and my gamecube has no serial 2 port...

tjanas commented 1 year ago

@danielkraak is there a way to force gc-loader to downgrade to a different firmware version upon system boot?

cvgc9 commented 1 year ago

same problem .

matt456 commented 1 year ago

similar issue here, latest Swiss prompted a GC Loader firmware update was available. Firmware update went as expected, it prompted to turn on/off Gamecube. Now it won't boot swiss or any other iso set to boot.iso on the SD card. Tried an SD card from another working GC Loader that still failed.

tjanas commented 1 year ago

Does anyone know how to get a hold of the developer of GC Loader?

danielkraak commented 1 year ago

Unfortunately, I do not believe it is possible to downgrade the firmware through the GameCube. I have received back one board that also no longer worked after the update, so I will look into this issue.

If you bought a GC Loader from gc-loader.com, feel free to use the contact form on the website for help with resolving the issue.

danielkraak commented 1 year ago

Also, sorry for the unresponsiveness. Usually I also receive a message through the contact form on the website to resolve these issues.

tjanas commented 1 year ago

Has anyone here had the issue with one ordered from Black Dog Technologies? For those with the issue, where did you obtain it?

cvgc9 commented 1 year ago

I ordered mine from Black Dog Technology. Worked fine before update 2.0.0. Tried multiple sd cards and installed in different GameCube . Wouldn’t boot .

AlexUnderBase commented 1 year ago

I have tried Mario Kart after updated from 1.1.2 to 2.0.0 and all went good ! My unit is from 1st batch sold on Black Dog Technologies , the one where ive did implant from cd drive of the gc cube connector to GcLoader unit

Let me know if anyone needs to try something here

Fdt8WkNX0AEkXFE 311967951_1187156202143821_6049373737458046671_n 310613160_555765653021315_1345200088155578894_n

isynx commented 1 year ago

Maybe updating from 1.2 to 2.0 is okay but not from 2.0beta Mine is also from black dog tech but I doubt if they will provide any easy solution

tjanas commented 1 year ago

@isynx have you contacted Dan at Black Dog Technologies to let him know about this issue?

isynx commented 1 year ago

I just wrote an message to them finger crossed

isynx commented 1 year ago

While still waiting for balck dog tech to reply, I wonder if by installing a picoboot can solve the problem. If I mod the console via picoboot, then I maybe able to boot and update (downgrade) the gcloader? Anyone has tried this and cares to share?

danielkraak commented 1 year ago

This most likely will not work. I have one GC Loader in my possession that does not work with 2.0.0 and it seems to lock out. As a result, it will not be able to process the update commands.

I will be looking into why it locks out in order to fix the issue.

Hagen76 commented 1 year ago

I'll stay in 2.0.0 beta on my two gc loaders until it will be safe to update^^ I really don't want to lock it. I've bought them from gc-loader.com!

tjanas commented 1 year ago

Any updates? Any word from Black Dog Tech?

isynx commented 1 year ago

Any updates? Any word from Black Dog Tech?

No reply so far. I would never update mine if given a second chance:s

Gitomata commented 1 year ago

Any updates? Any word from Black Dog Tech?

I think his pet dog passed away recently so he might be occupied atm. I think it's the same dog that appears on shop's logo.

Hagen76 commented 1 year ago

Any updates?

isynx commented 1 year ago

No replies so far. I am going to do a piboot instead

elgarlic commented 1 year ago

I had this problem with a previous GCLoader firmware update. "Turn the power OFF and check the NINTENDO GAMECUBE Instruction Booklet for further instructions." Dozens of attempted boots failed, while it had worked great on the previous firmware. I was told, "I'm guessing the new firmware doesn't meet timing constraints on your FPGA." (silicon lottery).

I unplugged the console for several hours and managed to get it to boot a single time. After that, it was back to failed boots. Repeated the process, unplugging, this time with a firmware downgrade in place on the memory card. Booted, downgraded, and working again. It may have been coincidence, as I was also told that unplugging should have had no effect. But it seems statistically unlikely that the two successful out of many dozens of attempts were done that way.

The next update was 2.0.0b, which was fine and is still working for me. Staying the hell away from 2.0.0 final. :)

j117-esc commented 1 year ago

I was about to upgrade until I saw this post. I guess we better stay on 2.0.0.BETA from the look of things.

g5star commented 1 year ago

I have had the same problem and I got mine from AliExpress. I believe I tried 2.0 version with mine and got the same results. I got error messages and now i get a dark blue screen on the tv. The GC Loader is the lite version It is V0.7 and was made in 2020. Does anyone know if you can reflash the Gc Loader?

elgarlic commented 1 year ago

I have had the same problem and I got mine from AliExpress. I believe I tried 2.0 version with mine and got the same results. I got error messages and now i get a dark blue screen on the tv. The GC Loader is the lite version It is V0.7 and was made in 2020. Does anyone know if you can reflash the Gc Loader?

The device you're talking about is a failed clone. They named it a GCloader lite because they couldn't even get it working to load games from its SD card, but they wanted to sell it anyway. So it should not be surprising if it fails to update or bricks, and it's not right to request support for clones from the developer.

tqhoang84 commented 1 year ago

I have an new-in-box GCLoader PNP (from BDT). Can the existing firmware be backed up & restored via a CH341A programmer? Any jumper to short/bridge first (like JP1 on the GCHD MK2)?

tqhoang84 commented 1 year ago

I have an new-in-box GCLoader PNP (from BDT). Can the existing firmware be backed up & restored via a CH341A programmer? Any jumper to short/bridge first (like JP1 on the GCHD MK2)?

@danielkraak - Is the firmware able to be backed-up & restored via a CH341A programmer (with 3.3V)?

abeisgoat commented 1 year ago

Just another data point - my GC Loader was bricked from doing the 2.0.0 update as well, tried many restarts with no luck. I've sent an email so we'll see how it is handled.

snowsensei commented 1 year ago

I went from 1.1.2 to 2.0 and, while it didn't brick my GCLoader, it created an issue where it would only boot into Swiss about one in 5 times I turned the console off and on again. I finally downgraded to the 2.0 beta and things have been fine. If it wasn't for the annoying notification that tells me there's an update available every time I turn it on, I'd probably never touch the firmware again.

elgarlic commented 1 year ago

I went from 1.1.2 to 2.0 and, while it didn't brick my GCLoader, it created an issue where it would only boot into Swiss about one in 5 times I turned the console off and on again. I finally downgraded to the 2.0 beta and things have been fine. If it wasn't for the annoying notification that tells me there's an update available every time I turn it on, I'd probably never touch the firmware again.

Yeah, the obnoxious nag screen is often the main downside. It should either appear only once or have an option to disable.

Apparently you can normally prevent it by editing the .ini. But of course the one exception to this seems to be 2.0.0.beta. https://www.reddit.com/r/Gamecube/comments/z4el6w/swiss_can_you_hide_the_gc_loader_firmware_update/

abeisgoat commented 1 year ago

Follow up from my last comment for anyone curious, after my GC loader was bricked by this update I went ahead and bought the $15 in parts to Picoboot it and that worked flawlessly and confirms that the GC Loader does not show up as a disk drive at all any more. Attempting to boot the GC Loader upgrade (or downgrade as it were) just freezes out.

tjanas commented 1 year ago

Has Black Dog Tech responded to this issue yet?

abeisgoat commented 1 year ago

Has Black Dog Tech responded to this issue yet?

@danielkraak last responded in October and has not replied to my email.

DIYdotexe commented 1 year ago

my GC loader was just bricked today by the 2.0.0 update. Why was it still available for download after it was a known issue? Has anybody heard from kraak or black dog?

elgarlic commented 1 year ago

my GC loader was just bricked today by the 2.0.0 update. Why was it still available for download after it was a known issue? Has anybody heard from kraak or black dog?

Sorry to hear that. No response. They've got none to sell due to the parts shortage. So it's not even a high enough priority to take the link down or offer a warning.

DIYdotexe commented 1 year ago

Uhh, if that’s true then it says a lot about how much they care about their customers

isynx commented 1 year ago

I guess this is a pitfall of all DIY projects. The maintenance cost is too high or the work is tedious. I still do hope there would be a solution but up to now it seems not very likely. Putting a warning besides the firmware 2.0 is definitely helpful to others who blindly update their firmware like me:p

JoeTheRetro commented 1 year ago

I was running the official 2.0.0 just fine, updated a couple of weeks ago for no reason other than noticing there was a new firmware. Dan posted on Twitter today and someone mentioned this problem. I just finished downgrading back to 1.1.2. I never had any problem on that firmware, so I figure better safe than sorry. What a bummer for those who have been bricked. I have a day one launch GC Loader. This must be affecting certain batches.

citrus3000psi commented 1 year ago

This seems to isolated problem which is why the firmware is still up. It could also be related to the update process itself. If you have purchased from black-dog and have a bricked 2.0 unit. Send me an email to me@dankunz.com and I will get you squared away.

tjanas commented 1 year ago

@isynx can you re-open this issue, since upgrading to 2.0.0 still has issues and there isn’t a newer firmware yet from @danielkraak to fix those problems?

snowsensei commented 1 year ago

Agreed. Especially since, for people who didn't buy direct from Black Dog, there is no fix.

isynx commented 1 year ago

I would like to reopen the issue but I don't find a way to do it. Maybe it is better to open a new issue. In my case, Dan sent me a replacement (I believe so) which has been updated to the latest firmware. Thus, my guess is that this is more hardware related lockup than something which can be fixed through an update. So try contact Dan and be patient, he will sort you out as long as you have a genuine gcloader.

danielkraak commented 1 year ago

I am looking into solving this issue. One of the major bummers is that some devices seem to randomly crash somewhere during startup, but it is not detected as an improper flash, so the recovery firmware does not boot. I will be adding additional recovery functionality, so it should always be possible to recover from this issue in the future.

KirovAir commented 1 year ago

I found this comment on reddit, it seems you can still downgrade your GCLoader even when it's bricked to fix it: Hey! I actually had the same issue and got the system to reflash the GCLoader. I put the disc drive back in and booted into Swiss via Paper Mario and a Hacked Save. Once I got into Swiss, I opened the PREVIOUS (not beta) update file with the disc drive still connected. The update software will detect firmware on the disc drive and then be ready to update At this point, I hot swapped the disc drive for the GCLoader. Then once it was connected, I pressed A, and it reflashed the GCLoader board with the previous firmware. Just be careful not to flash firmware while your disc drive is attached. Good luck!

caprisun08 commented 1 year ago

This is great! However I still would have to set up the exploit save with a modded wii correct? Is it possible to mount a pre existing exploited memory card that someone else has prepped? I do not have a modded wii close by.

danielkraak commented 1 year ago

I have just uploaded version 2.0.1.BETA to the repository. I am pretty positive that this will fix the issues. Black Dog Tech and I have tested this firmware on returned boards and all of them worked with this firmware.

It also has additional recovery options that can also recover from random crashes (as was happening 2.0.0, but they should also be gone now with this firmware).

I will keep the firmware BETA for now, but can hopefully kick it out of BETA soon. If there still happen to be problems, do not hesitate to contact me (gc-loader.com) or black dog tech and we will get your unit fixed.

snowsensei commented 1 year ago

Working great for me, thanks!

tjanas commented 1 year ago

I will keep the firmware BETA for now, but can hopefully kick it out of BETA soon. If there still happen to be problems, do not hesitate to contact me (gc-loader.com) or black dog tech and we will get your unit fixed.

Can you make a notification that it is now out of BETA? https://github.com/danielkraak/GC-Loader/issues/33

Shindur commented 1 year ago

Just wanted to comment that 2.0.1 release worked flawlessly on my GC Loader. It was having issues with 2.0.0, luckily I was able to revert it back to 1.1.2 until this new release came. Thank you everyone who worked on it!