Hacking Xenoblade Chronicle 3D xorpads

[blindseer]

I'll dump my xorpads again to make another rsf, but it'll take 4 hours for them to dump, the earliest I'll have it is tomorrow morning.

 

[Ichii Giki]

I'll dump my xorpads again to make another rsf, but it'll take 4 hours for them to dump, the earliest I'll have it is tomorrow morning.

No need to go through that trouble, I might have found my problem, but I do appreciate it!

I decided to test my rom file by running it through Gateway to make sure it was good and guess what, Gateway launched it but then I got the "Error has occurred" and was instructed to power down! So perhaps something went wrong in my original attempt to merge the files. Anyway, I merged the rom parts again and tested this newly merged rom and this time it launched from the Gateway menu and ran correctly. So I used method D again (with just the exheader xorpad) and am now installing a new CIA made from the correctly merged rom (this time with BBM, it seems to be installing a littler faster, should take a little over an hour instead of 1.5+ hours).

I will let you know the results shortly!

 

[Pacman`]

It should install properly on a 9.5 emunand using GW
The game needs a 9.4 f/w, btw

I installed "python-2.7.8.amd64 (Windows X86-64 MSI Installer (2.7.8) [1]).msi" on my PC.
I used 3DS To CIA Converter v4.1 and generated "ncchinfo.bin" using "2 - ncchinfo (Higher)" (NOT the "1 - ncchinfo (4.xx)" one).

I used Shadowtrance's Decrypt9.zip (http://gbatemp.net/attachments/decrypt9-zip.18855/) with the Ninjhax exploit on a 9.0.0 USA N3DS.
Put his Decrypt9 folder inside the Ninjhax 3ds folder.
Put "ncchinfo.bin" in the root
Put a working slot0x25KeyX.bin in the root (decrypt9 did open it).

You should get (after roughly FOUR (4) HOURS! - USE YOUR CHARGER):
000400000F700100.Main.exefs_7x.xorpad 4.0 MB
000400000F700100.Main.exefs_norm.xorpad 4.0 MB
000400000F700100.Main.exheader.xorpad 1.0 MB
000400000F700100.Main.romfs.xorpad 3598 MB
000400000F700100.Manual.romfs.xorpad 2.0 MB
000400000F700100.Partition7.romfs.xorpad 6.0 MB
and the Update xorpad which I always delete
(Copy your xorpads to a folder on your PC and keep them safe)

Now, 3DS To CIA Converter v4.1 can be tricky, but if you do what I did, it will work:

01- Copy your xorpads to the ROOT of the 3DS To CIA Converter v4.1 working folder
02- Copy your USA XC rom to the ROOT of the working folder, renaming it to an easy to type name, like rom.3ds
03- Run 3DS To CIA Converter.bat and Enter 3 for 3 - View Converters Menu
04- Enter 1 for 1- Start 3DS To CIA Converter (Req. Xorpads). It will ask for rom name, Enter rom.3ds (or whatever you renamed it to)
05- Do The Rest Automatically [Y/N]? Enter Y
06- It will then ask for input as follows:

1 - Continue Normally
2 - Alternative 1
3 - Alternative 2
4 - Alternative 3

Enter 4 for Alternative 3

07- Would You Like To Include The Manual [Y/N]? Enter Y
08- Let it do its magic...
09- Would You Like To Alter The Romfs Files [Y/N]? Enter N
10- Let it continue... (it will say Please Wait..) Be very patient here and let it finish to the end. You will eventually see a CIA Warning of some sort. It's normal.
11- Lo and Behold, you will find "rom (SDK5).cia" in the root of your working folder. Copy it to your mSD and execute it in your N3DS with BBM under GW.
12- You will also find a file "rom Results.txt" that will give very brief details of the procedure.
13- Enjoy!

Now, if you can't follow these very precise instructions, I would quit the scene

 

[blindseer]

No need to go through that trouble, I might have found my problem, but I do appreciate it!

I decided to test my rom file by running it through Gateway to make sure it was good and guess what, Gateway launched it but then I got the "Error has occurred" and was instructed to power down! So perhaps something went wrong in my original attempt to merge the files. Anyway, I merged the rom parts again and tested this newly merged rom and this time it launched from the Gateway menu and ran correctly. So I used method D again (with just the exheader xorpad) and am now installing a new CIA made from the correctly merged rom (this time with BBM, it seems to be installing a littler faster, should take a little over an hour instead of 1.5+ hours).

I will let you know the results shortly!

Well good luck, already dumping xorpads just incase, god I hope eventually they will speed the dumper up.

 

[Ichii Giki]

Now, if you can't follow these very precise instructions, I would quit the scene

Not any time soon! If I was able to region-change my regular N3DS EmuNAND to US and then manually transfer my saves from O3DS, I should be able to figure this out.

I guess the main problem just stemmed from combining the rom parts incorrectly (probably also why my ncchinfo.bin was messed up, since it was generated from the messed up combined rom). This is the first game I've tried to convert to CIA that is >2GB.

Well good luck, already dumping xorpads just incase, god I hope eventually they will speed the dumper up.

Absolutely! Another plus of using the Simple CIA Converter Windows executable as it only requires the exheader xorpad, although a downside of this conversion tool is it doesn't include things like Download Play (if the game has it; thankfully Xenoblade does not ).

CIA install at 38% and climbing!

 

[Pacman`]

Not any time soon! If I was able to region-change my regular N3DS EmuNAND to US and then manually transfer my saves from O3DS, I should be able to figure this out.

I guess the main problem just stemmed from combining the rom parts incorrectly (probably also why my ncchinfo.bin was messed up, since it was generated from the messed up combined rom). This is the first game I've tried to convert to CIA that is >2GB.



Absolutely! Another plus of using the Simple CIA Converter Windows executable as it only requires the exheader xorpad, although a downside of this conversion tool is it doesn't include things like Download Play (if the game has it; thankfully Xenoblade does not ).

CIA install at 38% and climbing!

Hi,

I was just kidding, cause I hate to explain things in detail and then nobody understands, hehe
Anyways, I hope you succeed

 

[Ichii Giki]

Success! Not sure if it was using BBM this time (probably not) or CIA made from re-merged rom files (probably so), but CIA installed and game runs fine, including manual! Thanks for everyone's input!

(Now to do more research into getting rid of update nag in EmuNAND...darn Nintendo Zones...at least the nag is pretty infrequent...)

 

[Ralph1611]

Success! Not sure if it was using BBM this time (probably not) or CIA made from re-merged rom files (probably so), but CIA installed and game runs fine, including manual! Thanks for everyone's input!

(Now to do more research into getting rid of update nag in EmuNAND...darn Nintendo Zones...at least the nag is pretty infrequent...)

I need this.

 

[drfsupercenter]

Ugh, so after waiting hours, I was left with nothing but a 34MB file called "s" on the MicroSD.

Any idea what happened? It said it was generating all the xorpads...

 

[blindseer]

You used a bad Python script to generate the ncch file, try finding a updated one, ie decrypt 9 should have one.

 

[drfsupercenter]

You used a bad Python script to generate the ncch file, try finding a updated one, ie decrypt 9 should have one.

I used the one from VOID's tool, can you link me to the proper python script? The Decrypt9 I downloaded only has the boot files, no scripts.

 

[blindseer]

I used the one from VOID's tool, can you link me to the proper python script? The Decrypt9 I downloaded only has the boot files, no scripts.

Here, this should work https://github.com/archshift/Decrypt9/tree/master/scripts

 

[gudenau]

So, does this split the files if they are greater than 2GB?

 

[drfsupercenter]

1.5 hours ouch!
yes, it could be your installer, i like devmenu, but failing that then fbi is nice.
if that is not the problem, then i can only imagine you did something wrong, as i saw the other xenoblades cias were made with it and they work.
download one, see if it works in fbi it might not be your fault




is the source here too? or just a windows executable?

All he did was take the source and change the 32-bit stuff to 64-bit, iirc. I suppose I could ask for the source.

 

[gbadl]

Do you guys think this game will be hackable at some point to run on a regular 3ds? Even if running it slower would be awesome.

 

[liomajor]

No chance.

 

[gudenau]

Do you guys think this game will be hackable at some point to run on a regular 3ds? Even if running it slower would be awesome.

nope.avi

There is no way this could happen, it even lags more than the Wii version. Now, if only we could use a 3DS and a New 3DS to get "six cores".

Offtopic:
Post 1000, yay?

Edit:
Here is a reason to the no:

Xenoblade is a verry intensive game, as such it uses more than what the 3DS had, allthough there is the special mode for Smash 3DS and Monster Hunter 4 (I think?) there is still the lack of raw horsepower. Sure the 3DS has more cores, but the Wii had a diffrent CPU all together and at a higher clock speed no less. (Wii PowerPC at 729MHz vs 3DS (2/4)xARM11 at 268MHz) If I recall corectly PowerPC (like in the Wii) has a better IPC than than ARM (like in the 3DS), which means that the times the clock must tick to preforme the same opperation is diffrent, lets say ADD takes 5 on ARM and 3 on PPC (made up numbers, but the point is there). There is also the fact that there instruction sets are diffrent, as an example on PPC to multiply two values in ram could be one opperations but on ARM it could be three. Now I do not recall if these diffrences are the same, but the main idea is there.​

​

There is also loss from the IPC, two processors doing the same work as one with the same "best case" time will never be the same. Making one CPU better than two if the one has the same raw numbers.​

​

There are some other problems that arw !uch more minor, but this is a big one.​

 

[motezazer]

So, undub update!
Packed with 3DS builder, my ROM was able to sucessfully pass the logo screen!
But I only get a black screen... (Even with edited fsize.dat)

 

[Kohmei]

So, undub update!
Packed with 3DS builder, my ROM was able to sucessfully pass the logo screen!
But I only get a black screen... (Even with edited fsize.dat)

Have you tried simply rebuilding with the same files to make sure it isn't a problem with the rom building process?

 

[motezazer]

Have you tried simply rebuilding with the same files to make sure it isn't a problem with the rom building process?

Black screen when using original files.
Weird, because I'm sure it's not the rom building process...
Perhaps the fragmentation?