I hope not... I mean I just took out of the box and follow directions from this guy:
Screen garbles after OSINIT or turns white or black. Is there ANYTHING i can do??? I'll be really really pissed off if I bricked by this.
I hope not... I mean I just took out of the box and follow directions from this guy:
Screen garbles after OSINIT or turns white or black. Is there ANYTHING i can do??? I'll be really really pissed off if I bricked by this.
Great. I don't believe this is even my fault. Any advice on returning it back or getting a refund? I do really want this flashcard.
Mine is still on the most recent official one, works fine for me with games I want to play.
Can't see any reason to upgrade unless I need to ie. Fix a game I play that has an issue fix, or adds a feature I need, and then only after its been proved safe
I don't see why people always want to jump onto most recent beta firmwares unless they need to or asked to do so by the developer
Sent from my SM-G965F using Tapatalk
Can't see any reason to upgrade unless I need to ie. Fix a game I play that has an issue fix, or adds a feature I need, and then only after its been proved safe
I don't see why people always want to jump onto most recent beta firmwares unless they need to or asked to do so by the developer
Sent from my SM-G965F using Tapatalk
- Joined
- Jan 22, 2015
- Messages
- 535
- Trophies
- 0
- Age
- 44
- Location
- Military base.
- Website
- colorslive.com
- XP
- 650
- Country
Yea after the RTC stuff was fixed for the official Pokemon games I quit updating because they was working on alot stuff that I had no interest in yet
In the meantime I released a new version of the RTC test ROM: https://github.com/aaaaaa123456789/rtc3test/releases/tag/v002
I don't think there's much point in doing the range tests if the basic tests already fail, but for when those start working, that's out there.
I don't think there's much point in doing the range tests if the basic tests already fail, but for when those start working, that's out there.
Hi @Urbanshadow , so sorry to hear that, you can try this.
-Reformat you microSD to FAT32 and 32kb of cluster (Yes, again)
-Use the last Frimware and Kernel from the official EZ-Flash web (Firmware 4 & Kernel 1.04e), copy only the Frimware and Kernel files to your microSD
-If you can, pair it with a fast microSD card (class 10)
-Use batteries in good shape
-If asked, DON'T set the "autosave" to tilted (At least NEVER if the "SAVER" folder is not created yet by the system, this can lead to enter into a loop)
-For now, DON'T try to configure the RTC or autosave, we just want to get to run the "Update_FW4.gb" update (in this case to downgrade)
If by a miracle you were able to boot to the menu, flash this Firmware "Update_FW4.gb".
(When flashing, never press any button, when it finishes, turn off/on the system)
If none of this is working, you can try the same steps, but with Firmware & Kernel "FW5K105RC.zip" from the comment #405 and try to flash the "Update_FW5_7-31.gb"
If you still the same after all, you can also try to remove the battery (ONLY IF YOU KNOW WHAT YOU'RE DOING) and after a couple of minutes put it back and try again the steps above
Notes:
-When everything is prepared, try to boot several times to try to get to the Flash card menu
-Use every Update file with it's respective "ezgb.dat", even if they have the same size, they are different
(UPDATE: You can use the ezgb.dat from "FW5K105RC.zip" and "Update_FW4.gb" from Offical web)
-When finish updating, power off/on the system, never use the reset button of the cartridge for this particular task
I hope something of this helps you, and if not, let's wait for the EZ-Flash team to see if they can help with this issue. Cheers mate
And @Urbanshadow just for the record, What is your test system? it has any mod?
-Reformat you microSD to FAT32 and 32kb of cluster (Yes, again)
-Use the last Frimware and Kernel from the official EZ-Flash web (Firmware 4 & Kernel 1.04e), copy only the Frimware and Kernel files to your microSD
-If you can, pair it with a fast microSD card (class 10)
-Use batteries in good shape
-If asked, DON'T set the "autosave" to tilted (At least NEVER if the "SAVER" folder is not created yet by the system, this can lead to enter into a loop)
-For now, DON'T try to configure the RTC or autosave, we just want to get to run the "Update_FW4.gb" update (in this case to downgrade)
If by a miracle you were able to boot to the menu, flash this Firmware "Update_FW4.gb".
(When flashing, never press any button, when it finishes, turn off/on the system)
If none of this is working, you can try the same steps, but with Firmware & Kernel "FW5K105RC.zip" from the comment #405 and try to flash the "Update_FW5_7-31.gb"
If you still the same after all, you can also try to remove the battery (ONLY IF YOU KNOW WHAT YOU'RE DOING) and after a couple of minutes put it back and try again the steps above
Notes:
-When everything is prepared, try to boot several times to try to get to the Flash card menu
-Use every Update file with it's respective "ezgb.dat", even if they have the same size, they are different
(UPDATE: You can use the ezgb.dat from "FW5K105RC.zip" and "Update_FW4.gb" from Offical web)
-When finish updating, power off/on the system, never use the reset button of the cartridge for this particular task
I hope something of this helps you, and if not, let's wait for the EZ-Flash team to see if they can help with this issue. Cheers mate
And @Urbanshadow just for the record, What is your test system? it has any mod?
Last edited by RetroKarl,
Wow what an amazing response. I'll try everything you said and let's hope.
I own a GBA with a backlight mod where I originally updated. I also own a GBP for the GC. Would that be any safer? I can try to do everything on the GBP.
Now that I think about it, the cart battery may be dry. I remember the popup. Would that be dangerous during upgrades?
Last edited by Urbanshadow,
I just noticed that you have them listed in your description banner... haha (Sorry). Ok, well, that's away from ideal, but, well, if it was working at least once in the GBA (when you updated previously), I think it will be a good idea to do it in the GBA. I really don't have any info on the compatibility with the Gamecube GBP. If you can ask a friend or have some way to get a stock GBC-GBA to test, that will be better.
Last edited by RetroKarl,
It's a stock GBA but the video output goes to the GC and the GC inputs go into the GBA. Nothing magic.
Yes, I know the GC GBP, but it's a similar concept to the Super Gameboy and Super Gameboy 2 (And they both have issues with this card) so I don't know if it will work.
But if you don't get luck with the GBA, you can try it in the GC GBP.
About the battery, It's not very likely to be dry. Almost every time that you install-reinstall Firmware or copy new Kernel files to the microSD. On the first boot, this alarm shows up. Also when you remove and reinstall the battery, the alarm shows up. So, every new EZFJr shows it on first boot.
Last edited by RetroKarl,
After 300 or so attempts I got to the blue Battery Dry!!! popup actuable with A. It crashed by pressing A, but hey, something got drawn.
This was with the FW4 and a class 10 SD, like you suggested. I don't have much hope, but I'll keep trying.
This was with the FW4 and a class 10 SD, like you suggested. I don't have much hope, but I'll keep trying.
Wow, that's a lot of attemps O.o . If you have on hand your GC GBP maybe it's worth trying.
Edit #1: And what's exactly the behaviour of all the attemps? OSINIT stuck? If so, give it some time (a copuple of mins), maybe it's loading but very slowly.
Edit #2: Yep, but I still think that if these cards are just semi-bricked, maybe like Ninoh-FOX suggested, an auto-update Kernel can be plausible. A modded Kernel to bypass the OS menu to run the only GB-GBC game in the card (the FW Update). But I'm talking from the ignorance, not a programmer here.
Last edited by RetroKarl,
I got it with the GBP using GBI High Fidelity because reports itself as a GBA instead of a GBP so I suppossed it would be more compatible and I can't have the battery problem in the GBP haha.
It should be possible to do a GBA multiboot updater. The internal cartridge switch won't switch back to GB mode during multiboot, has 256Kb of maximum rom size (plenty enough for the version 4 firmware) and would re-flash the carts without a menu working. Everything would be easier.
Last edited by Urbanshadow,
Sorry for double post, but I just want to report success on unbricking the card, thanks to the help of @RetroKarl and @EZ-Flash2
On a sidenote, the GameCube's GBP works great as a test system, especially when paired with GBI hf version.
On a sidenote, the GameCube's GBP works great as a test system, especially when paired with GBI hf version.
Last edited by Urbanshadow,
Well that's great! @Urbanshadow
Just for the record, what was the most effective Firmware & Kernel to unbrick your card? The official from the web?, or the one of the comment #405?
And BTW all this info that you're giving on the behaviour and performance of the GC GBP with the EZFJr is new info, cheers for that. For sure it will be useful in the future for someone else.
Just for the record, what was the most effective Firmware & Kernel to unbrick your card? The official from the web?, or the one of the comment #405?
And BTW all this info that you're giving on the behaviour and performance of the GC GBP with the EZFJr is new info, cheers for that. For sure it will be useful in the future for someone else.
Last edited by RetroKarl,
Then I can say the link cable functions with the GBP also work flawlessly. Just got some starter pokemons to my original crystal cart.
The most important part is the SD, I used a 32GB sdhc sandisk ultra formated as FAT32 with 32K unit size. The rest is trial and error. I took about 5 hours with rests resetting the cart every 10/20 seconds from the internal reset button or the GC reset (fast power cycle).
The files used were the 1.05RC ezgb.dat and the update (downgrade) gb file from FW4.
A good news for the guys who were humming SGB compatibility.
It's been a while since the last update. and while we were waiting for the Prism crew to fix his Junior, some kind Chinese user lent us a set of SGB, but..........
We've found that Junior's development board won't fit into the SGB slot without damaging the SGB cases, as it has a lot of wiring connectors on the development board . So we still need time to modify the development board.
SGB compatibility is hopefully added to this FW5 final release.
In other good news, the Prism developer @aaaaaa123456789 just sent word that his Junior has been fixed.
Similar threads
-
@
Maximumbeans:
Man, that's beyond my brain
I'm no good with hardware for now. I'd like to get into hardmods in future though -
@
SylverReZ:
@Maximumbeans, Maybe start practice soldering. Get a cheap-ass soldering iron and follow some good YouTube tutorials.+1 -
@
SylverReZ:
Least my experience has gotten better than over a decade ago. My iron would constantly bump into components and break them.
-
@
Maximumbeans:
Sounds good. I actually did soldering but like 16 years ago for school so uuuuh probably rusty haha
-
@
SylverReZ:
@Maximumbeans, Same here. I did soldering at school from a teacher who I honestly liked since he had plenty of good electronics experience.+1
-
-
-
-
-
@
SylverReZ:
It was like all clear and fancy. Tbf I'm not too experienced with chess, but would like to learn someday.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
