Is My Gp2x Bricked?


CloudStrife

Still Fresh
Joined
Aug 25, 2006
Messages
32
I just got my GP2X this morning, and I've read by many users that firmware 2.1 is the most stable firmware. So mine came as firmware 3.0, I reformatted my SD card (canon 4GB) and loaded up the 2.0 files, I followed the instructions on the GP2X site and then started to downgrade the firmware. Everything went perfectly fine, the firmware flashed and I was at the GP2X menu, the screen with games, music, etc. So then I powered down the device, and now when I turn it on I get a black screen, and the power light is on. Thats it, just a black screen. I flashed the firmware using the official AC adaptor. I am so lost, nothing went wrong it flashed correctly as I was able to use the menu, but as soon as I turned it off and tried to turn it back on, I get a black screen and a the green power light. This sucks, can it be fixed? Thank you!

EDIT: Now when I power on the device I see little black lines like there bleeding.
 
Yes, 2.1 is the best, but if you already have 3.0, it's not worth the risk to downgrade.

As for your problem however -- dead batteries?
 
It's not dead batteries, I tried freshly charged batteries, and new alkalines too, same thing. I've been using the AC adaptor for everything though. And thanks RX Shorty, but the difference is that you get a GP2X splash screen, I just get a screen with black horizontal lines, and I wasn't using a CPU/LCD-Tweaker either.
 
I can't flash the firmware either, no matter what I do, I just get that damn black screen with horizontal lines :(
 
woogal said:
And the moral of the story is 'If it aint broke...'
Exactly, had he looked around he would've seen that a 3.0->2.0 is not a clever thing to do at all. I'm guessing that you have destroyed u-boot. When you flashed it at first, whatever bootloader you have installed at the time boots the OS. Since it's already in RAM, it doesn't matter that it's been deleted. When you next turned back on u-boot was corrupt, so it can't do anything. Send it to somebody who knows what they're doing and get it reflashed.
 
Last edited by a moderator:
Now that just sucks, I really regret doing that now, but OMG my first firmware experience, and it killed the whole thing, I only got to use the 2x for like 10 min. But I did check around, I didn't see anyone having problems downgrading it.
 
Hmm so you put the Firmware files in the Root of your SD?
And used the button combo to start the Flashing process?
But the screen keeps beeing black...

Try to do the steps (Flashing your GP2X) with a black screen... wait for a minute or 10 and reboot it.

But what I think your LCD screen is broken... :(
 
RX Shorty said:
Hmm so you put the Firmware files in the Root of your SD?
And used the button combo to start the Flashing process?
But the screen keeps beeing black...

Try to do the steps (Flashing your GP2X) with a black screen... wait for a minute or 10 and reboot it.

But what I think your LCD screen is broken... :(
Whoa... how would the LCD die on me?! *worries*
 
Last edited by a moderator:
RX Shorty said:
But what I think your LCD screen is broken... :(
I doubt it. I've edited a possible explanation into my above post. It certainly isn't the kernel, if it were you'd get the initial splash screen first. A kernel problem would cause a hang at the green screen.

http://www.gp32x.de/board/index.php?s=&am...st&p=549894
http://www.gp32x.de/board/index.php?s=&am...st&p=548637
http://www.gp32x.de/board/index.php?s=&am...st&p=545885
http://www.gp32x.de/board/index.php?s=&am...st&p=530273
http://www.gp32x.de/board/index.php?s=&am...st&p=531591
http://www.gp32x.de/board/index.php?s=&am...st&p=525901
I've been trying to put the message out that downgrading 3.0->2.0 is a really bad thing to do if 3.0 works fine for you, but time and time again people ignore it.
 
Last edited by a moderator:
RX Shorty said:
Found another link you could walk through: Here

Think it is your kernel indeed... Reflashing would solve it...



I have tried that, but I'm unsure if I did that correctly. Would you know exactly what I would have to do to reflash a kernel?
 
Last edited by a moderator:
Orkie said:
RX Shorty said:
But what I think your LCD screen is broken... :(
I doubt it. I've edited a possible explanation into my above post.

I've been trying to put the message out that downgrading 3.0->2.0 is a really bad thing to do if 3.0 works fine for you, but time and time again people ignore it.


Hehe that includes me... I had lucky I guess... Well had to reinstall the FW about 3 times :D
And you are right about the LCD, it is the kernel I think. :)

Edit:
Sorry can't help you with reflashing your device :(
 
Last edited by a moderator:
CloudStrife said:
I have tried that, but I'm unsure if I did that correctly. Would you know exactly what I would have to do to reflash a kernel?
Put gp2xkernel.img on the SD and hold start+select at bootup. It won't work though, you'd get something on your screen if it were. I do think it's the bootloader, and to repair that you will likely need to send it to somebody (like EvilDragon) to fix (or buy a cradle, but the cradle's JTAG connection doesn't guarantee a successful unbrick from such a downgrade).
 
Last edited by a moderator:
EvilDragon live's so far away too, and I'm broke. I live in New Jersey and EvilDragon is like in a galaxy far away lol.
 
Hmm that is hard.

Don't you have anybody close to you with a Cradle?
You could PM Evildragon if you could send it to him, then again it costs money...
Sucks to be so unlucky, sorry man...
 
Back
Top