Pokemon HeartGold and SoulSilver Translation Patch.

[Death Insurance]

Hm so it seems I'm not the only one having Rom crashing problems. >_>
For me, it happens after I try to battle someone after goldenrod city and attempt to save. :P

[Dash]

There is one problem I am facing with New Version 5.
When I save the Version 5 Heart Gold game in R4 with actual NDS and transfer that save file to No$GBA that runs Version 5 Heart Gold game, the No$GBA won't load the save file. It notes that rom-image has crashed. With the unpatched Japanese version I could transfer the saved file from NDS R4 to No$GBA with no problem at all.

this is what you ned bud its what i use from no$gba to acekard2i

http://www.shunyweb.info/convert.php#

easy to use

edit for kazo

here is a offical list of the items well key items everything else seems to be fine

http://serebii.net/heartgoldsoulsilver/items.shtml

[Sora_145]

Why is the "patched.nds" such a small file?

Looks like the patcher is crashing instead of finishing.

[Orcamania5]

this is what you ned bud its what i use from no$gba to acekard2i

http://www.shunyweb.info/convert.php#

easy to use

edit for kazo

here is a offical list of the items well key items everything else seems to be fine

http://serebii.net/heartgoldsoulsilver/items.shtml

Yeah, I already tried that website you have given me before I posted previous message. and guess what. The No$GBA still says the rom-image has crashed when I attempt to load Heart Gold save file from R4 to No$GBA.

The save file itself is not corrupted because when I put saved file from R4 to DESmuMe it worked. However it brings another question if No$GBA emulator is corrupted, but of course it is not. Since, the both save file and No$GBA are working properly, why would I get "rom-image crash" message?

[Parma]

Hmm. Well, I fixed my problem. I have no idea if this will help those who use flashcards and the such, but for us Nogba players, this SHOULD solve it all.
Save problems, crash problems.. say goodbye:

1. Patch your Nogba here if you've never done it: http://cscomputing.org/downloads.php?cat=8 (No more AR code!)

2. Get the three files: dsbios7, dsbios9, and firmware.bin. I dunno if I can tell you where to get these, but use Google. -- Set it up so it loads from bios. (Goodbye crashes!!)
3. Patch Rudolph's and Kazo's patches SEPERATE. I can't even load the game with the pre-combined one. (See ya save problems!)
4. Of course, set your save type to Flash512K, just for safety. (??)

If you did this right, your Nogba should run for at least four hours without ANY defects... I've yet to play longer than that..
If this doesn't work for anyone, let me know. Because it worked wonders for me.

[Dash]

Yeah, I already tried that website you have given me before I posted previous message. and guess what. The No$GBA still says the rom-image has crashed when I attempt to load Heart Gold save file from R4 to No$GBA.

The save file itself is not corrupted because when I put saved file from R4 to DESmuMe it worked. However it brings another question if No$GBA emulator is corrupted, but of course it is not. Since, the both save file and No$GBA are working properly, why would I get "rom-image crash" message?

well as long as you place the sav in the battery folder in the no$ you should be fine the rom is acting up what i would say is delete it from the comp and replace that rom with the one from your r4 bud and see what happens

[PsychoCarebear]

Heya, just wanted to say thank you for the awesome patch!!!!
I don't understand ANY Japanese, and so thought that i wouldn't be able to play Pokemon HG/SS until it's released next year. BUT thanks to your patches, the game has now been playable for me!

The only thing that I'm wanting now, is translation of the phone calls i keep getting, and of the radio channel that tells you about where the swarms are (Prof. Oak's channel).

You're doing excellent work!!! Keep it up A+++++

[Orcamania5]

Hmm. Well, I fixed my problem. I have no idea if this will help those who use flashcards and the such, but for us Nogba players, this SHOULD solve it all.
Save problems, crash problems.. say goodbye:

1. Patch your Nogba here if you've never done it: http://cscomputing.org/downloads.php?cat=8 (No more AR code!)

2. Get the three files: dsbios7, dsbios9, and firmware.bin. I dunno if I can tell you where to get these, but use Google. -- Set it up so it loads from bios. (Goodbye crashes!!)
3. Patch Rudolph's and Kazo's patches SEPERATE. I can't even load the game with the pre-combined one. (See ya save problems!)
4. Of course, set your save type to Flash512K, just for safety. (??)

If you did this right, your Nogba should run for at least four hours without ANY defects... I've yet to play longer than that..
If this doesn't work for anyone, let me know. Because it worked wonders for me.

I will try that sometime in the future. If that method doesn't work for me I probably have messed up the 3rd step cause I didn't quite understand what you said. Reason why is I thought the Version 5 patch patches both Rudolph's and Kazo's at the same time. If it should be patched seperately, can you tell me how?

well as long as you place the sav in the battery folder in the no$ you should be fine the rom is acting up what i would say is delete it from the comp and replace that rom with the one from your r4 bud and see what happens

I already performed that method. I directly copied the rom and the save file from R4 to No$GBA folder. I put the directly copied save file to 'Battery' folder and rom in No$GBA folder -> still no luck. Oh yeah, and I set my save setting for the emulator to "FLASH 512kBytes" + the AR code for anti-black screen (from the first post in this thread).

[Parma]

I'm sure I made a mistake on that..... I'm not sure. I think the prepatched one didn't work because I didn't encrypt it... I'll test this as soon as I repatch everything.

But on the first page here, there's two options: v5 Patch and v5 + Rudolph's
The v5 Patch is just Kazo's. The other one includes Rudolph's.
http://www.megaupload.com/?d=K32R0HU5 --- This is Rudolph's patch sep. from Kazo's.
Of course, you'll need to run Rudolph's then Kazo's and all that..

I also did the arm7 fix with a Japanese Platinum as the donor. That's running flawless as well.

I really have no idea about flashcarts, I wish I could help specifically.. but yeah.

(But..
One more test. An un-touched, clean SoulSilver rom, running with no AR code, nothing.
Just a patched Nogba 2.6a running on bios. We'll see how this goes.)

Okay, here's the end all Nogba fixes:
Patch your Nogba where I said in my previous post. Your game will still crash running on bios if you don't have this, as far as I know.
Get ndsbios7, ndsbios9, and firmware.bin. Run Nogba from the startup point GBA Bios.
Make sure your rom is encrypted. This should fix ALL Nogba problems. A clean SS and just Kazo's patch run perfect on this setup.

OR.... take the easy route, download my Nogba folder and just rename your save to
Pokemon Soul Silver (P).SAV and replace the one already there. --- The "file" on it is patched with the arm7 fix, Rudolph's patch, and Kazo's translation. I uploaded it only after I assured COMPLETE stability. So if THAT doesn't work, then I dunno.. but here's the URL.
"This zip does NOT contain a rom... roms are illegal."
http://rapidshare.com/files/28325841...S_and_save.zip



Edit: On Nogba, if you switch your savetype without loading your save file, it won't recognize it.
What this means is, you'll need to start up your game, switch save types, save options in Nogba but DON"T reset it... save your game. Then exit. Now you have a Flash512k .sav

Again, tell me if I'm wrong, because I'm going on what worked and didn't work for me.

EDIT: Clean (but encrypted) SoulSilver J rom does NOT crash on a patched Nogba running bios. At least during a stress test (in an out of buildings, in and out of the pokegear and pokedex. Constantly saving.) I'll continue testing this along with a rom running just Kazo's patch. If everything turns out fine, it'll mean the arm7 fix and Rudolph's patch are obsolete. Also, the prepatched one did in fact not work because it was decrypted. Ran enDSryptS on it, and it loaded from bios. Pfft.

[Orcamania5]

OR.... take the easy route, download my Nogba folder and just rename your save to
Pokemon Soul Silver (P).SAV and replace the one already there. --- The "file" on it is patched with the arm7 fix, Rudolph's patch, and Kazo's translation. I uploaded it only after I assured COMPLETE stability. So if THAT doesn't work, then I dunno.. but here's the URL.
"This zip does NOT contain a rom... roms are illegal."
http://rapidshare.com/files/28325841...S_and_save.zip

Thanks for the information you had written and the hard work you did for me, PARMA. (and DASH for answering to my problem also.) I give a great praise to you. I followed the patch of emulator and all does bios/firmware. and guess what? I managed to load the save file in No$GBA! No more crashing-image problems from now on. ^^

I'll continue testing this along with a rom running just Kazo's patch.

I don't think you have to do this for me cause thanks to you, the problem is gone.
The steps I took to do it was...
1) Patch the clean HG/SS rom with Kazo's Version 5 patch using "xdeltaGUI"
2) Bring the patched rom to the program that does the NDS rom encrypting
3) Encrypt the patched rom
4) Turns out to be a success at loading save file that was brought directly from R4

[SA2]

New patch can cause a card to fail and erase most things, and to not be recognised by computers anymore. Use at own risk.

[PsychoCarebear]

Ive been using it since it was released, without any issues at all. chances are that your flash memory failed at about the same time as you updated it with the patched HGSS. my old 1GB kingston microsd card failed while i was playing pokemon platinum, but it was unrelated to the ROM.

[eighty4]

New patch can cause a card to fail and erase most things, and to not be recognised by computers anymore. Use at own risk.

xD

No it can't.

[SA2]

xD

No it can't.

Uh, yes, it can.

It happened to me. :/

Luckily I fixed it though.

This is what happened;
http://www.gbatemp.net/index.php?showtopic=174723

[PsychoCarebear]

Uh, yes, it can.

It happened to me. :/

Luckily I fixed it though.

This is what happened;
http://www.gbatemp.net/index.php?showtopic=174723

That wasnt caused by the patch. I've seen that happen on old USB flash drives. It's just simply that it's failing, or you pulled it out of the computer when windows was still trying to access it. (ie. without safely removing" it first)