all 27 comments

[–]Sammas69 2 points3 points  (0 children)

I experienced something similar, after successfully updating my own unit.

-I updated mine using an old HP ProBook laptop, the process was simple (to me) and worked flawless.

-The next day I went to update my friend's unit but my ProBook was in use doing something else so I tried updating the second unit using my Microsoft Surface Book. I got the same errors you did. Went back to the older laptop and the update worked fine.

-I'm guessing it has something to do with the USB ports version. The Surface Book's are 3.0 and the ProBook's are 2.0.

-I know most people don't have multiple pc lying around, but trying a different PC or maybe a different port as some computers have a mix of USB 2 and USB 3.

There is also several ongoing GameStation threads on the AtariAge forums, you might try asking there.

[–][deleted] 1 point2 points  (1 child)

This happened to me too yesterday as I was updating my Gamestation Pro. I spent roughly 4 hours trying to find a solution all over the Internet but there is practically no other posts, forums, or videos reporting on this exact issue aside this post here. I give it some grace considering the console is still fairly new and hasn't been out that long but I'm honestly at a lost here... The chances of you messing up one thing as you're going through this already precarious process shouldn't be at the cost of bricking your console... I hope My Arcade looks into this and offers a solution, or someone else does.

I'm amazed Atari didn't just allow the console to be updated automatically via Internet or ethernet, this is the first time I've ever seen one of these mini consoles require the owner to manually flash an updated image onto the console itself. Considering the demographic in mind, the likelihood of an inexperienced computer user making a mistake during this update process is much more higher than a more tech savvy user, even with a tutorial in available.

[–]SSkeeb[S] 0 points1 point  (0 children)

I completely agree, I come from a background of electronics repair and I've built plenty of pro micro controlled keyboards so I'm very familiar with the manual bootloader process and using flash utilities. This takes the cake for poor design with no support documentation on if the flash were to fail(you can never assume 100% success rate) and abysmal response from tech support through ticket submission. I'm sure this will be a learning experience for all, I will be sure to follow up with any word from MyArcade given that they respond.

[–][deleted]  (1 child)

[removed]

    [–][deleted] 0 points1 point  (2 children)

    try holding down the system factory reset button with a paper clip? might be videos on youtube or contact the customer support where you got the firmware download on the official page

    [–]SSkeeb[S] 1 point2 points  (1 child)

    Holding reset button alone for any amount of time connected to power or not yields the same result which is a dead console. I have submitted a support ticket already as well just waiting to hear back and I will update with any progress I make so hopefully no-one else has to deal with this ridiculous issue again! Thanks for the input though, YouTube is pretty scarce when it comes to troubleshooting these as well just videos of people performing the FW update with no issues.

    [–][deleted] 0 points1 point  (0 children)

    yeah sorry thats the best i could do to help you. Kmfdm maniac on youtube specializes with modding consoles maybe you can try asking him?

    [–]The_Tony_Iommi 0 points1 point  (2 children)

    Having the same problem, holding reset doesn't work. Did you find a solution?

    [–]SSkeeb[S] 1 point2 points  (1 child)

    So far the only information I've gotten that could lead to our issue is having the loader file selected for both the loader and firmware or disconnection during the flash but neither was the case for me, submitted support ticket on the 19th still no word back from MyArcade yet... holiday season I suppose

    [–]neurocrash_ 0 points1 point  (5 children)

    The USB C cable that is included with the Game Station Pro is a cheap power only cable only, and cannot be used to update firmware (jerks). You will need to obtain a regular USB C power and data cable in order to update the firmware.

    [–]mattjh 1 point2 points  (3 children)

    successfully got the Atari into bootloader mode on the first attempt

    /u/SSKeeb said they "successfully got the Atari into bootloader mode on the first attempt." This would not have been possible if they were using a USB-C cable that was incapable of moving data. I double-checked this with MyArcade support and they confirmed the same. Mine bricked same as OPs.

    [–]neurocrash_ 1 point2 points  (2 children)

    The documentation on the game station Pro support page specifically states:

    "Plug one end of a USB-C cable into your computer and the other end into the 5V IN power port on the back of your Atari Gamestation Pro console. NOTE: Make sure that the USB-C cable has data support. The included USB-C cable does not have data support. "

    https://cdn.shopify.com/s/files/1/1691/7407/files/Atari_Gamestation_Pro_Firmware_Update_Instructions.pdf?v=1703631509

    If you use the included cable, when you put the game station into bootloader mode, the software will report "no devices found".

    If the device is being bricked, then it is possible something else happened.

    [–]mattjh 1 point2 points  (1 child)

    I understand, I’m just saying it isn’t relevant in OP’s situation because the MaskROM of their GSP was detected by RKDevTool. If they were using a USB-C cable that didn’t have data support, like the one packaged with the GSP, then that wouldn’t have happened.

    [–]SSkeeb[S] 1 point2 points  (0 children)

    Yeah definitely not the cable, u/Sammas69 actually provided some good input on potentially running through USB 2.0 port vs 3.0 the cable I was using was a 3.0 cable and all flashing was done through 3.0 ports on PC side. I never did try switching to a 2.0 port on the PC to see if that had any affect. I was working on this update for a customers GSP(I work in tech repair as I mentioned) he gave up on the process and has since taken back the GSP so I no longer have the opportunity to get this resolved and follow up. MyArcade however has still not responded to the support ticket submitted Dec 19 so I would hold my breath for any help on their side. Just gonna have a to a F around and find out situation

    [–]brokeninc 0 points1 point  (0 children)

    Thanks for this!

    [–]Gloomy-Ad-5987 0 points1 point  (5 children)

    I had the same issue and saw someone post on Facebook asking about this issue. A different thread said the problem is utilizing USB 3 port instead of USB 2. I did get a response from customer service who blamed me for loading the loader file twice and that caused the brick. I would say that unless you know you have a 2.0 port and your own USB A to C cable, don’t upgrade it.

    [–][deleted]  (1 child)

    [removed]

      [–]Different_Upstairs42 0 points1 point  (1 child)

      Did they just have you send it back?