Hacking [Release] rxTools - Roxas75 3DS Toolkit [fw 2.0 - 9.2]

[lPolarisl]

Is it still possible to get one of the old versions ?

 

[PKNess]

Is it still possible to get one of the old versions ?

I have 2.0 if you want it.

 

[lPolarisl]

I'd rather have one of the 1.x, since they seem to work better... I can't get the rXMode to work :/

 

[jmmc]

I'd rather have one of the 1.x, since they seem to work better... I can't get the rXMode to work :/

rxMode was introduced in 2.0 and some emunand wasn't detected.

Maybe if someone has 2.0.1... But you can't run SSB or MH4

 

[lPolarisl]

Oh... So, no solution to my problem yet, right ?

 

[jmmc]

Oh... So, no solution to my problem yet, right ?

Do you have firmware.bin, slot0x25KeyX.bin and the GW emunand?

 

[Xelnok]

Just wanted to be sure about one thing before i start using this. I have an eShop pokemon Y save from my original 9.2 sysnand that contains all of my legit pokemon that i could never transfer to the bank without updating, i was also never able to access that save utilizing mt card because my sysnand needed to be 4.5.

With this tool i could restore my 9.2 sysnand with the original save game, create a new emunand, update that emunand to the latest firmware and be able to access my original save game and the bank at the same time?

Does the emunand tool work with this?

The steps would be use the gateway tool to restore sysnand to 9.2 (where i know the game works without any corruption issues), load up rx tools, format emunand and then update to the latest firmware. Would formatting the emunand somehow mess up my pokemon save game, or could i reinject my 9.2 nand backup into my emunand to make sure the save works?

One last question, could i access the 9.2 sysnand whenever i want to be able to use the browser exploit with my pokemon games and then switch over to the latest emunand and still have access to the pokemon save game? i.e. switching back and forth between sysnand/emunand in order to utilize the browser explot

Thanks alot.

 

[DSoryu]

Just wanted to be sure about one thing before i start using this. I have an eShop pokemon Y save from my original 9.2 sysnand that contains all of my legit pokemon that i could never transfer to the bank without updating, i was also never able to access that save utilizing mt card because my sysnand needed to be 4.5.

With this tool i could restore my 9.2 sysnand with the original save game, create a new emunand, update that emunand to the latest firmware and be able to access my original save game and the bank at the same time?

Does the emunand tool work with this?

The steps would be use the gateway tool to restore sysnand to 9.2 (where i know the game works without any corruption issues), load up rx tools, format emunand and then update to the latest firmware. Would formatting the emunand somehow mess up my pokemon save game, or could i reinject my 9.2 nand backup into my emunand to make sure the save works?

One last question, could i access the 9.2 sysnand whenever i want to be able to use the browser exploit with my pokemon games and then switch over to the latest emunand and still have access to the pokemon save game? i.e. switching back and forth between sysnand/emunand in order to utilize the browser explot

Thanks alot.

Yes to all, I did the same and it works now .

 

[Apache Thunder]

Any one have v1.0/v1.1? I can't get the current version to decrypt my 3DS files. Unless it expects them in a specific folder? I use the decrypt CTR titles menu, but it just says "decrypted 0 files".

 

[Slushie3DS]

Isn't archshift the guy who developed Decrypt9? Any other 9.2 user with the white screen issue?

Yep, i can make a function to import ticket.db in the emunand, so all the titles present in the sdcard will result installed.

Sd decryption, along with the Ctrdecryption option to browse folders and choose single files are in the todo-list

Pretty sure he is, yes.

Can you elaborate more on the part I put in bold? Much appreciated.

 

[Roxas75]

Ok guys, i'll relook at the 9.2 launching method, i quite have the idea of what the problem can be. I'll release a fix for that.

I'll also look at the code of ctrdecryptor which checks the encryption flags.


About ticket.db, it's just a way to share the installed titles between sysnand and emunand.

 

[Slushie3DS]

Ok guys, i'll relook at the 9.2 launching method, i quite have the idea of what the problem can be. I'll release a fix for that.

I'll also look at the code of ctrdecryptor which checks the encryption flags.


About ticket.db, it's just a way to share the installed titles between sysnand and emunand.

So, with the tickets, I would be able to install something from eShop to my emuNAND, and it would work on my sysNAND? That'd be convenient, even as I have gotten used to launching rxMode as I launch my 2DS. Still a great idea.

 

[Apache Thunder]

Yeah I'm trying to decrypt a Pokemon X rom. But current version of rxTools doesn't see it. Pokmon X does not use the 7.x encryption I believe. Perhaps it's not detecting older encryption type 3DS files?

Also, I have not had issues launching rxTools with this version. I have 9.2.0-20U sysnand firmware. Have not had it fail to start and rxMode worked the last time I tested it.

 

[Slushie3DS]

Y

Yeah I'm trying to decrypt a Pokemon X rom. But current version of rxTools doesn't see it.

Also, I have not had issues launching rxTools with this version. I have 9.2.0-20U sysnand firmware. Have not had it fail to start and rxMode worked the last time I tested it.

Oh, you finally managed to get 9.2? I take it that the you picked through the UpdateCDN .CIA.

 

[Apache Thunder]

Y
Oh, you finally managed to get 9.2? I take it that the you picked through the UpdateCDN .CIA.

Yeah, basically all one has to do is update a 4.x emunand using CIAs from UpdateCDN/3DNUS, then use rxTools to inject a working 9.2 firm0/firm1.bin file into emunand. Then that emunand partition is ready to be flashed to sysnand. That's basically what I did. This does require you have firm0.bin/firm1.bin dumped from an working 9.2 sysnand image. As long as it's the same region, the firm0/firm1 files shouldn't be unique to each console, so you can use one from a different one provided that it was dumped using rxTools since rxTools will decrypt it for you and re-encrypt it when you import it. Just make sure you have the slot0x25KeyX.bin file as I'm not sure if the firm0/firm1 partitions will be encrypted properly without it if you booted rxTools from 4.x/5.x/6.x sysnand.

 

[Roxas75]

The maybe it's a matter of region.
For the users who have issues when launching rxTools 2.x, please report both system version and region.

 

[Apache Thunder]

Could be that the firmware.bin downloader is downloading firmware.bin for the wrong region for some users? I'm USA region, so it works fine for me.

 

[Slushie3DS]

Yeah, basically all one has to do is update a 4.x emunand using CIAs from UpdateCDN/3DNUS, then use rxTools to inject a working 9.2 firm0/firm1.bin file into emunand. Then that emunand partition is ready to be flashed to sysnand. That's basically what I did. This does require you have firm0.bin/firm1.bin dumped from an working 9.2 sysnand image. As long as it's the same region, the firm0/firm1 files shouldn't be unique to each console, so you can use one from a different one provided that it was dumped using rxTools since rxTools will decrypt it for you and re-encrypt it when you import it. Just make sure you have the slot0x25KeyX.bin file as I'm not sure if the firm0/firm1 partitions will be encrypted properly without it if you booted rxTools from 4.x/5.x/6.x sysnand.

Jeesh, that's a lot for 9.2.

 

[Apache Thunder]

Yeah. You have to do that for any firmware that uses the new encryption. (unless you have a retail game with that update)

Updating 3.0 to 4.x or 4.x to 5.0 should still work. But 6.x or higher will result in bricks because firm0/firm1 isn't being updated correctly when you are in Gateway/MT-Card mode or the Palantime CFW. It's either the exploits or perhaps a flaw with DevMan that results in this. But game roms fail to update firm0/firm1 correctly as well, so I'm leaning more towards an encryption related issue with newer firmwares. System Settings can still update sysnand correctly though...

I was able to exclude the update for TWL_FIRM and DC Cart Whitelist, so I can still use my Gateway blue cart on 9.2. (one user even reported that his AceKard2i still worked after this). So even those already on 9.2 might benefit from this.

 

[Slushie3DS]

Yeah. You have to do that for any firmware that uses the new encryption. Updating 3.0 to 4.x or 4.x to 5.0 should still work. But 6.x or higher will result in bricks because firm0/firm1 isn't being updated correctly when you are in Gateway/MT-Card mode or the Palantime CFW. It's either the exploits or perhaps a flaw with DevMan that results in this. But game roms fail to update firm0/firm1 correctly as well, so I'm leaning more towards an encryption related issue with newer firmwares. System Settings can still update sysnand correctly though...

From what I am gathering, I would not be able to do that on 8.1 because it is higher than 5.0?