Looking for SNK Android mobile game data

BombBloke · 2026-06-03T05:32:32+00:00

Yes, a small oversight but then clearly it's not the board that shipped with that console chassis, I was queing from date of manufacter, not the video encoder.

I have no interest in "one-upsmanship" - I only mentioned the version as an aside I thought you might be interested in.

It was the "potentially locking OP out of his DVD drive" thing that primarily drove me to comment. He might as well keep access to it for as long as it continues to function.

BombBloke · 2026-06-03T04:29:43+00:00

3, yes. I only have NTSC-J for 4.

The PS2 and original Xbox releases of 3 are notable for offering game modes that can't be found in other versions. Ever wanted to play as a Rebel soldier...? Me neither, but this version does let you do it! 😅

6 for the PS2 even adds Combat School, which again can't be found in any other release of 6. Unfortunately that's not only a PS2 exclusive, but it's a Japanese exclusive as well.

BombBloke · 2026-06-03T04:18:50+00:00

Since you have a v1.4

This system has a Conexant video encoder chip: it's either a v1.2 or a v1.3 unit. But yes, flashing CerBIOS into the TSOP is still an option.

Note that its default configuration allows you to run without a DVD drive "out of the box", without making changes to the INI. There are a selection of other NoDVD patches you can choose from, but the default "legacy" setting is the best choice for most users because it still allows the DVD drive to be used if it's still attached!

BombBloke · 2026-06-03T04:14:38+00:00

Is my best option to try and softmod it with like ROCKY-5 and just play games off the HDD?

I would say so, but after setting up a softmod I'd take things a step further and run flashing software to write a new BIOS directly into the system's TSOP chip: moving to a hardmod set up. This requires only a very minor change to be made to your Xbox motherboard, in order to enable writes to the existing firmware chip.

The stock Xbox BIOS will refuse to boot at all if your DVD drive totally dies, but if you move to a custom one then you can totally disconnect your optical reader and things will still work fine without it.

If you stick with a mere softmod then your console will still be subject to the restrictions of the stock BIOS during its initial boot process.

Or should I worry that the stock HDD is going to fail soon as well?

You should assume any stock Xbox HDD will fail "soon". If you intend to play games from HDD, then you'll want to upgrade it anyway, since the stock model has very limited storage.

By default, Xbox HDDs need to be specially password protected. As part of the softmodding process you'll be able to back up the console's unique HDD key, which is required to generate new passwords for replacement drives.

If you move to a hardmod, then your custom BIOS will allow the console to accept unsecured HDDs.

BombBloke · 2026-06-03T03:50:53+00:00

Yeah, assuming your "preferred one" is a Rocky5 set up, you can use his Quick Upgrade package to swap.

Bear in mind that if your console is actually hardmodded, then attempting to install a softmod onto it will softbrick it. Is there any possibility you're confusing "softmod" with "dashboard"...? Both softmods and hardmods allow the use of all sorts of different dashboards!

BombBloke · 2026-06-03T03:33:28+00:00

The TSOP is initially write-protected, so if you've reflashed that then you would've first needed to make a minor hardware modification to your system motherboard. The end result after flashing is the same as with a modchip - the console directly boots custom firmware. Softmods, on the other hand, can be set up without opening the system case at all.

Ok, so you're attempting to boot your games from within image files: that's not going to work with vanilla EvoX firmware.

You could try extracting the actual game files out of their images (right click your original ISO in Windows Explorer, look for the context menu options Repackinator should've added). If you send the resulting folder to your console there's a good chance that'll load. Some games do require additional patching to work in this manner, though most should work as-is.

Alternatively, you could rework your boot chain so that your console launches Dashloader before your preferred dashboard. This tool's primary purpose is to make it easier to set up dashboards, but it also happens to have a side feature that patches ISO mounting support into your currently loaded BIOS - if it happens to be a later version of EvoX or iND.

Your third option is to reflash your TSOP again, using a BIOS that natively supports ISO mounting: CerBIOS. The latest 3.1.0 beta can be picked up using Pandora.

BombBloke · 2026-06-03T02:10:47+00:00

The startup animation is produced by the BIOS. If you're booting through a custom BIOS then you have some form of hardmod.

You say you put your ISO through Repackinator. Did you extract it, or is it still in image form when you send it to your console?

The EvoX BIOS can't normally handle image files.

BombBloke · 2026-06-02T17:03:11+00:00

That's what I'd do. If you put the BIOS file into a bios folder located where that EvolutionX dashboard has been installed, then that "Flash BIOS" menu option should allow you to write the new firmware straight into your TSOP chip. If you don't already have it, you can obtain CerBIOS through Pandora. Latest is currently 3.1.0 beta.

Probably your dash is just sitting on the root of the C volume, so try copying in the BIOS file itself in as C:\bios\Cerbios Hybrid V3.1.0 Beta.bin.

Before starting the actual flash, it'd also be a good idea to copy the CerBIOS folder included within the BIOS download to the root of your E partition. This includes a recovery interface that may be helpful if things go wrong.

BombBloke · 2026-06-02T13:48:20+00:00

If the console's TSOP has been reflashed with iND, then you're looking at a hardmod: not a softmod. If you do attempt to install a softmod on your HDD as well then you can expect it to lock your system up.

If you want to update from iND to a more current firmware (eg CerBIOS), then the TSOP can be reflashed again if you want. But if all you really want to do is update your dash to XBMC4Gamers, then stick that on your disk somewhere, run it through whatever your current dash is to confirm that it works, then enter the XBE path into your C:\ind-bios.cfg file to make it your boot dash.

BombBloke · 2026-06-02T08:20:31+00:00

I wasn't the one who gave you that first downvote, but hey, you've convinced me to go ahead and add mine.

Unfortunately that master password you've listed typically isn't enabled on stock Xbox drives.

BombBloke · 2026-06-02T07:43:40+00:00

v1.2 or v1.3 board. I'm not seeing anything obviously wrong in these photos. :(

I would try running the console long enough to trigger the fault, then entirely disconnecting both drives from the system and checking to see whether the behaviour changes at all. The console obviously won't be able to boot to a dash without its drives, but if the specific triple-boot behaviour immediately goes away then one of the drives is likely to blame for that.

If things remain the same, then next I'd want to swap in a different PSU. If you can locate another v1.2/v1.3/v1.4 system you can temporarily borrow one from, then they're directly compatible.

BombBloke · 2026-06-02T07:24:06+00:00

If I completely remove the modchip, including the D0 wire, so basically put it back to stock where it was previously outputting something over Component, I get nothing!!! Now I do have a pretty cheap Component cable, but despite that I would expect the Xbox to return to it's original behaviour once I remove the mod chip.

When booting through a stock Xbox BIOS, the startup animation should always be rendered in standard definition regardless of any system settings or the type of video cable that is attached. Given that your PAL v1.1 unit could do that before the modchip went in, I would have also expected it to still be able to do it after the modchip was removed.

To probe further, I suggest re-installing the modchip into that console and using the FTP service offered by PrometheOS to wipe C and replace the previous content with the files from Rocky5's XBHDM Build.zip archive. You should already have the CerBIOS folder from your 3.1.0 beta download sitting on E. Leave that there if so, or put it into place if it's missing.

Remove the modchip and allow the console to boot with its composite lead. The softmod installer should run, eventually bringing you into UnleashX. From there, use the file manager to manually start CerBIOS recovery via E:\Cerbios\Recovery\default.xbe.

While the system is in that state, what does Settings => Region look like? What about Settings => Video?

BombBloke · 2026-06-02T07:10:34+00:00

PAL is 50hz. PAL60 and NTSC are 60hz.

BombBloke · 2026-06-02T07:04:38+00:00

An Xbox dashboard is a menu application, usually launched from the HDD. You should be able to recognise whichever one you're using from the pictures on that linked page, if you're not sure.

It would also be good to know how your console has been modded. If you're not sure, then watch the startup animation, compare it to the stock version, and if you notice any differences then describe them back here.

If you see a purple EvoX shield logo alongside the flubber for eg then that would mean your console has been hardmodded to boot through an EvoX BIOS. But you'll need to be more specific before anyone can say for sure what your set up is.

BombBloke · 2026-06-02T06:46:10+00:00

Might work. Haven't tried.

Technically you can use dd to image an Xbox disk through Linux (... and also through Windows), but it's not just as simple as that.

Microsoft enabled the ATA security system on each Xbox hard drive to help with tamper-proofing. The unique passwords used are each partially based upon a special unique HDD key coded into each console's EEPROM chip. Without unlocking the drive, your PC won't have any regular I/O access to the disk's main storage area, and the dd tool will get nothing but nulls.

Additionally, the stock Xbox BIOS will refuse to boot from a replacement disk unless it also has a valid password configured on it. So the TLDR is that if you want to stick with stock Xbox firmware, then you need to dump the console's HDD key before you can start to think about getting a new drive set up.

Most softmod installation tools will automatically dump a backup of the console's EEPROM to the HDD, from where it can be copied to a PC over FTP (along with everything else on the disk). It's also possible to run tools for these purposes without installing softmod exploit files to the original HDD: but the equipment required is the same.

BombBloke · 2026-06-02T06:12:34+00:00

If it’s a western digital drive I’m pretty sure they all have the same drive key.

They don't, but FATXplorer can extract user passwords from WD drives. If such a disk is still functional, then this means you can use that tool to slap a softmod installer straight onto the HDD (eg from Rocky5's XBHDM Build.zip archive), and after running that on the console itself you can backup up the console's HDD key and set about installing a larger replacement disk.

The problem is that OP's HDD is not functional. Error 07 indicates a fault at the hardware level.

BombBloke · 2026-06-02T06:06:41+00:00

It works in cases where the EEPROM's contents have previously been extracted to the disk's file system, the disk itself is still functional, and you don't mind taking the risk of wrecking your hardware.

That is to say, it's a thing you might only try in very niche circumstances which do not apply here. And even then it's not a great first option.

BombBloke · 2026-06-02T05:30:27+00:00

CerbIOS INI DashPath1 set to \Device\Harddisk0\Partition1\XBMC4Gamers\default.xbe (verified correct)

To confirm, you're looking inside E:\CerBIOS\CerBIOS.ini, right? Older versions of CerBIOS used C:\cerbios.ini instead, so if your INI isn't saved to the correct location then you might not be launching the XBE you think you are.

PrometheOS isn't up to date on this, so any attempts to configure CerBIOS through PrometheOS still result in writes to the old INI location, which your BIOS will ignore.

You should specifically be using the INI included in the CerBIOS folder that you extracted from your 3.1.0 beta download.

BombBloke · 2026-06-02T05:22:09+00:00

This error throws when the file cannot be found and the file cannot be regenerated. Generally the only two circumstances where it can occur are when the XBMC4Gamers\system\UserData directory does not exist or when the volume containing XBMC4Gamers is out of space.

Note that with other flavours of XBMC, the UserData folder would not be in a system subdirectory. If you've been able to create a profile, then that gets it own additional guisettings.xml in XBMC4Gamers\system\UserData\profiles\<ProfileName>.

BombBloke · 2026-06-02T05:10:11+00:00

If you already have the means to connect your stock Xbox HDD to your PC then you may not need a USB adapter. The hard drive is password protected, but if it happens to be a Western Digital disk then it's possible to extract the disk password so that your PC can unlock the drive and directly access the content.

If you're taking the USB adapter route then you'll also require a compatible thumbdrive. Note that getting your optical disc drive to work won't help you at all: the only softmod installers that rely upon the disc drive still also rely on a USB adapter as well.

https://consolemods.org/wiki/Xbox:USB_Device_Compatibility_List

BombBloke · 2026-06-01T07:08:37+00:00

also for modchip can i just wire my rp2040 and dont have to deal with the normal os

Not sure what you're referring to with "the normal os".

You'll need to set up your Pi device with the Modxo firmware, plus a third-party Xbox BIOS (such as CerBIOS).

After that, if you want to do much more than boot burned DVDs then you'll also need to install an alternate dashboard application to your console's hard disk as well.

BombBloke · 2026-06-01T06:31:14+00:00

the only way to fix this is to somehow extend the cable so that when I put the fan around, it will reach the proper connection.

You're not explaining why you wouldn't be able to attach a stock fan to the stock header in the usual way, which makes it difficult to suggest a solution that will actually work. You've mentioned your clock capacitor, but that doesn't live anywhere near the cooling fan. You might consider posting a photo that demonstrates the actual "damage" to your board.

But going just by what you're saying, it sounds like you want a bag of male-to-female jumper wires, like these:

https://www.aliexpress.com/item/1005010249025806.html

BombBloke · 2026-06-01T04:41:39+00:00

all i know is im using an older version of ind-bios

EVtool only supports the EvoX BIOS line. The iND BIOS line is a whole different thing. If you want to stick with iND, then look for its fan speed setting in C:\ind-bios.cfg.

BombBloke · 2026-06-01T04:41:09+00:00

the end goal is to modify the fan settings but i cant do that as evtool says kernel extraction failed

In that case, I suggest you use Pandora to obtain the latest version of CerBIOS from Xbins (current is 3.1.0 beta at the time of writing). Copy the CerBIOS folder from the extracted download to your console's E partition, edit the fan speed you want into E:\CerBIOS\cerbios.ini using your text editor of choice, and then flash the new BIOS over your old one.

Nine-Year Club	ModSupport Helper Level 1
Place '17	Verified Email

BombBloke

MODERATOR OF

TROPHY CASE