Gameshell won't boot past logo screen

check the assembling and try again
make sure the sd-card is ok
if all went failed

email to

Thanks for the reply. So I left the unit on last night, when I go check on it this morning, it still only shows the logo screen. I guess we can rule out the OS auto expand storage part.

How do I check if the SD cards are OK on windows 10? When I plug it into the card reader, it won’t show anything because I’m on Windows, if I plug it in use usb cable while SD card in the gameshell, still nothing.

I’ll send email to support too.

Normally it should show something, if flashed correctly it should have 2 partitions and one of them, the boot one is fat so its windows recognizable.

Try to flash with win32diskimager

I always had success with that program.

1 Like

Thanks, I’ll try to flash again use win32diskimager later today.

Also, I believe that partition wizards like can see what is going on with the SD. Usually I use those to resize, check, format things.

I tried flash the OS image using win32diskimager this time. Still the same result, don’t really know if this is software related or hardware related issue. :frowning:

Try removing all the components besides the mainboard and the LCD, even removing them from the plastic sub housing.

Also just for fun, try alternative OS releases.

It shouldn’t make a difference, especially seeing as you’re using a stock SD card, but I recall another user here having trouble installing the stock OS on a 400GB card, and having it fill up the space. He had success using my image somehow.

Thanks for your reply, I tried these two OS. The custom D.E.O.T. one has the same result as the stock OS. The Arch Linux also stuck, however, this time I get some logs.
Here is a screenshot of the arch Linux OS, about 2 hours after boot. I don’t have any knowledge of linux, does anyone know about those logs? Thanks.

you only put the first (boot) partition on your sd card, it miss the second one with the system

like the log said : “/dev/mmcblk0p2 does not exist”, mmcblk0 mean first sd card reader, p2 mean partition 2

how did you flashed the os on the card ?

1 Like

I downloaded the file, use 7z to unzip it, then use the win32DiskImager to flash file to the sd card.

never tried this tool but it seem the device dropdown show you logical device ( ie C:\ and co ), maybe not hardware ones ? it may have writed the full image (or what it can) only on the first partition of the sd card ?

how many time took the flash process ? it must be pretty long has the image is 8GB
on the last hand boot partition just have few Mb, so be pretty fast to fill it

you may also try unmount the sd card partition from your os file manager before the write

if issue still here have a try with another sd card reader

1 Like

Possibly try Etcher. It’s the program that comes up a lot as the defacto flashing program.

1 Like

Etcher seems to only recognize those img files, not the beta file like the Arch Linux OS.

The flashing process indeed took quite a while, last times it took me about 15 mins to flash the OS to the sd.

If you change the extension to img you’ll be good.
Did it work using etcher for any other images?

1 Like

Ok, i changed the file extension to img and it’s flashing now. Etcher works for other images.

So the sd I’m using is a 64Gb one, I decided not to touch the 16Gb one comes with Gameshell as a backup. After flash, it will create a boot partition about 40mb, and another partition that is not recognizable by windows. Does that sounds right? Just wanto make sure I’m not doing something terribly wrong flashing.

Sounds perfect!

Looks like it was a problem with how you used the win32diskimager program, as @r043v mentioned.
I’ve never used it, so cant vouch for its reliability.

Did the stock 16GB card ever work for you?

Wait hang on! I just read your original post!
Put in your original 16GB card, plug in the power via USB, hit that reset button and then try and power it on. It should work, with external power.

Also try updating to the latest version of etcher. There were some reports of earlier versions being incompatible.

Just finished flashing the Arch Linux OS again using Etcher, still the same error message. There must be something wrong with the flashing process I guess.

The stock 16SD card, the offical 0.5OS, custom OS created by you which I flashed on to the new 64SD card all have the same problem, can’t get past the GameShell logo.

I edited my previous post with a couple more paragraphs while you were writing your reply! Haha. But yeah. Try external power. I’ve had a similar scenario occur to me, and this fixed it.

Now I have the original SD card inserted, connected to external power supply, pressed the reset button. Still the same logo :cry:

Etcher is the latest version which I just downloaded yesterday.

Using etcher should solve your partition writing problems since it writes the entire image including partitions.
As @r043v try a different card reader, or even another physical computer. I personally use the SD reader built into my MacBook Pro, using a SD micro to SD adaptor.

Let etcher do it’s verification thing to make sure the image was done properly. Also make sure you eject the card properly when removing it.

Another thing. Try holding the power button for ages. Like 20 seconds. Also try holding the power button, then pushing the reset button. I don’t know if there is any official hard reset rescue me combo, but this would usually be it.

I’m not sure if it’s been assembled the whole time, but also try having the battery disconnected for a few minutes then trying again. Then try having it plugged into USB power for a while, then giving it a shot. I’m thinking re: battery calibration problems.

Occasionally I have had my unit power on to show the splash screen, then just go black. I attributed that to the fact that I have worn out my battery, ie leaving things to compile for days on end, and not having enough current to push through the boot process.

On the note of not enough current, check your cable leading from the battery to the mainboard. Really make sure it’s pushed in, and that the wires aren’t pushed out of the headers of anything. Also, make sure you’re using a dedicated USB micro charger, say a 5A one.