Homebrew NSUI Problem with Pokémon for gba

TurdPooCharger · Jul 12, 2020

Skepy said:
@TurdPooCharger I tried to fix by checking the sd using the windows Error Checking because only the 3ds folder was corrupted and not the entire sd, and now all software reappeared.

After you inject and test saving on those other Pokemon games and Sanyo save type, you should go back recheck the SD card you're using for hardware problems. If this happened on your main SD card, follow steps 1–4 in post #11 on that card. Replace it if the result comes back [BAD].

Skepy said:
Only one thing, after I try pokemon, can you link me a post (if exist) to regenerate the 3ds folder without having to reinstall all software?

This serves a similar role to Rebuild 3DS Database but through a PC or computer. It requires basic familiarity with Python.

rebuild-title-database

It's the companion program to one of ihaveamac's other works.

custom-install - Install CIAs to a Nintendo 3DS SD card entirely on PC

I've haven't use rebuild-title-database before, so can't give you firsthand insight in what's it like. Having used his other programs like ninfs, his python script is hands down going to be way faster and more efficient than my gm9 script at fixing/rebuilding the SD card's title.db.

Why use one over the other? That'll depend on the user's comfort level punching in easy command lines or ownership of a computer that runs Python.

Skepy said:
@TurdPooCharger
I tried and this are the results:
- Sanyo save type freezes
- Europan Fire Red works, but it's in english
- Pokemon Leaf Green (Italian) doesn't wok and it freezes

so the problems are the italian roms, oof

EDIT: I have the original cartridge, but I can't dump it so I can't find a working rom I thinkg

Double check the hashes of these two pokemon *.gba roms but this time in SHA256.

Pokemon - Versione Rosso Fuoco (SHA256: AD52B593EF0C7439E1409D3F0A1EC3FF865A494CA46C2184FE65573759838F3A)
Pokemon - Versione Verde Foglia (SHA256: C71599A482C43DF2104CE6BE903393333D3EBACBF392EA5FCD8792DADA8A5076)

This is to be extra sure your copies of the roms are definitely good dumps.

If they match, that means it's not the games but something wrong with the o2DS system itself.

Shomy · Jul 12, 2020

@TurdPooCharger the test for the sd went good so it doesn't have problem now

Now I'm checking the rom and I will let you know if the problem are this

EDIT: They match, but I still don't know why it does this only with the Italian Fire Red and Leaf Green, Emerald works and also Fire Red in English...

TurdPooCharger · Jul 12, 2020

Skepy said:
@TurdPooCharger the test for the sd went good so it doesn't have problem now

Now I'm checking the rom and I will let you know if the problem are this

EDIT: They match, but I still don't know why it does this only with the Italian Fire Red and Leaf Green, Emerald works and also Fire Red in English...

Well, last chance... Here's hoping that this Pokemon - Fire Red / Leaf Green save bug is a fixable software issue. Refer to the CTRTransfer (Type D9) - CTRTransfer back in post #15.

Outcome (C) If that 3DS firmware repair works, your o2DS might have had frankenfirm where the AGB_FIRM (~~3DS~~ GBA firmware) is outdated or had a partially corrupt *.app.

-or-
Outcome (D) If the CTRTransfer (Type D9) does not work, o2DS is a lemon! :hateit:

***

EDIT - Gonna sign off. Gotta go on grocery shopping errands. Will reply later. Ciao!

ghjfdtg · Jul 12, 2020

There is a possibility all of the dumps floating around are bad and mistakenly marked as good dumps but what is even the chance? On the no-intro db there are 2 dumps listed both with matching hash. So either your 3DS is somehow broken (but then it should cause problems with other games too) or it's the SD card/card reader since you already got corruption.

Shomy · Jul 12, 2020

TurdPooCharger said:
Well, last chance... Here's hoping that this Pokemon - Fire Red / Leaf Green save bug is a fixable software issue. Refer to the CTRTransfer (Type D9) - CTRTransfer back in post #15.

Outcome (C) If that 3DS firmware repair works, your o2DS might have had frankenfirm where the AGB_FIRM (~~3DS~~ GBA firmware) is outdated or had a partially corrupt *.app.

-or-
Outcome (D) If the CTRTransfer (Type D9) does not work, o2DS is a lemon!

***

EDIT - Gonna sign off. Gotta go on grocery shopping errands. Will reply later. Ciao!

I don't think I'm gonna try this method for now, because it's too risky for me now

--------------------- MERGED ---------------------------

ghjfdtg said:
There is a possibility all of the dumps floating around are bad and mistakenly marked as good dumps but what is even the chance? On the no-intro db there are 2 dumps listed both with matching hash. So either your 3DS is somehow broken (but then it should cause problems with other games too) or it's the SD card/card reader since you already got corruption.

I tried with another sd and it did the same thing so the only thing can be my 3ds

I can only hope someone that can check this by installing my same cia

Shomy · Jul 13, 2020

@TurdPooCharger I ask to a friend to install the same cia as me and on his 3ds it worked the rom, so the problem is my 3ds

Another problem, it won't turn on, there's the blue led but on the screen there isn't nothing
But gm9 and luma works

EDIT: Now it boot up, it was the flashcart that won't make it boot, but the problem remains my 3ds for the game

TurdPooCharger · Jul 13, 2020

Skepy said:
@TurdPooCharger I ask to a friend to install the same cia as me and on his 3ds it worked the rom, so the problem is my 3ds

Another problem, it won't turn on, there's the blue led but on the screen there isn't nothing
But gm9 and luma works

EDIT: Now it boot up, it was the flashcart that won't make it boot, but the problem remains my 3ds for the game

I have no other advice to offer except to try fixing the 3DS firmware with the CTRTransfer (Type D9). If you're not comfortable following the Instructions or find it too difficult to understand, you can try translating that page.

CTRTransfer (Type D9) {Google translated into Italian}

Or try copying and pasting the steps to this website.

DeepL Translator

First try reading and familiarizing the Instructions before deciding to go through with it. I ~~can make no~~ cannot promise it'll fix the save bug.

Shomy · Jul 13, 2020

@TurdPooCharger i arledy did the ctrnand trasnfer using 3ds.guide, but I also backuped some files with Decrypt9, so now I only need to restore all the tickets, the problem is that I don't know how to do it xD

TurdPooCharger · Jul 13, 2020

Skepy said:
@TurdPooCharger i arledy did the ctrnand trasnfer using 3ds.guide, but I also backuped some files with Decrypt9, so now I only need to restore all the tickets, the problem is that I don't know how to do it xD

Decrypt9(WIP) CTRTransfer , GodMode9 CTRTransfer (aka, "standard / defacto / official ctrtransfer") , and CTRTransfer (Type D9) are not the same thing.

I'm terribly sorry, but you basically messed up your o2DS even more now by bricking the DS(i) mode, delisted any DSiWare games you had installed, erased the HWCAL0/1.dat screen calibration files (image quality is going to look like shit), deleted your user profile setup, and lost any made eShop purchased legit tickets.

Had you followed the Instructions as advised in post #15 and this didn't work out as planned, any changes caused by CTRTransfer (Type D9) would have been reversible with that sysnand *.bin image like as if nothing happened.

Unless you backed up a sysnand *.bin image just before doing Decrypt9 & GodMode9 CTRTransfers, some of those unwanted changes can't be fixed not even by CTRTransfer (Type D9).

Shomy · Jul 13, 2020

@TurdPooCharger uh.. I have a sysnand backup sooo, If I restore it, it will work again?

TurdPooCharger · Jul 13, 2020

Skepy said:
@TurdPooCharger uh.. I have a sysnand backup sooo, If I restore it, it will work again?

It'll restore the state of the 3DS firmware and user profile to how it was exactly when that image was created. That means new friends added to the Friend List, Activity Log, StreetPass / SpotPass, Mii characters, Notes, DSiWare games + saves, and other private user data that were gathered after making that image will not return.

Shomy · Jul 13, 2020

@TurdPooCharger ok, I'm restoring it

After it restores, I need to follow the guide on the previous post right?

TurdPooCharger · Jul 13, 2020

Skepy said:
@TurdPooCharger ok, I'm restoring it

After it restores, I need to follow the guide on the previous post right?

Follow the Instructions only if you believe there's still a small chance that CTRTransfer (Type D9) can fix the Pokemon - Fire Red saving problem.

I don't want to get your hopes up but be ready to accept that your o2DS may be a lemon like Vinniemeneer's o2DS in that other thread.

I wish I knew why this happens on o2DS systems with Pokemon - Fire Red/Leaf Green and related romhacks but unfortunately don't have the answer or solution to every conceivable 3DS/2DS problems. At the end of the day, homebrew and custom firmware has their limits to what can be done.

Shomy · Jul 13, 2020

@TurdPooCharger I did everything and it seems to be all ok, except for... Pokemon Fire Red.... Sometimes it let me enter the game, but mostly of the times same problem.....

TurdPooCharger · Jul 14, 2020

Skepy said:
@TurdPooCharger I did everything and it seems to be all ok, except for... Pokemon Fire Red.... Sometimes it let me enter the game, but mostly of the times same problem.....

Sorry this happened to you.

Do you own a ntrboot compatible DS flashcart like one of these models listed in this chart image?

I can only offer two theories as to why this o2DS does not work with Pokemon - Fire Red (Italian version).

Theory #1 - The eMMC (NAND chip) has cell defects where it can't properly load the AGB_FIRM or its agbsave.bin partition. There's a way to test this, but I rather you don't try to if don't own or can't borrow a ntrboot flashcart from a friend.

Theory #2 - The ARM CPU/SoC is the component that has a ever so slight defect where it can't properly run or simulate all of the GBA firmware. There is no way to directly test this theory but to assume from observation that since everything else works, your o2DS has a bad brain when it comes to running in ARM7+ARM9 modes.

Not much else we can do except switch over to GBARunner2 or open_agb_firm for that specific game (see post #15), get a different/another 3DS system, or replace the o2DS motherboard.

Shomy · Jul 14, 2020

@TurdPooCharger unfortunately I don't have it, so as you said, the only thing I can do is to use GBARunner2 because changing the motherboard doesn't have any sense lol, I can take directly a new console

Anyway thanks for the help tough it didn't work

Homebrew NSUI Problem with Pokémon for gba

Meh.

Active Member

Meh.

Well-Known Member

Active Member

Active Member

Meh.

Active Member

Meh.

Active Member

Meh.

Active Member

Meh.

Active Member

Meh.

Active Member

Similar threads

Popular threads in this forum