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

[pakrett]

It works for me (emuNAND 9.9 + Rxtools 3.0b6)

Oh god you're right, it works ^^ It can fail but it works.

Edit : and it works in sysNand rxMode too, but I found it harder too make it work than on devmode.

 

[noctis90210]

just a question here guys, the rxtools with pasta devs was in vacation for 2 weeks, its already 2 weeks have passed but why i cant see them posting in this thread about any development or plans?

 

[pakrett]

just a question here guys, the rxtools with pasta devs was in vacation for 2 weeks, its already 2 weeks have passed but why i cant see them posting in this thread about any development or plans?

First --> Because they do what they want.
Second --> Only @AlbertoSONIC was in vacation for 2 weeks, @motezazer for one month.
Third --> Even if they are not on vacation, it means they are working, so I guess they have their priorities, right ?

(Just wait and don't be worry, they will surely return soon...)

Edit : Anyway, the next step is new3DS support.

 

[AlbertoSONIC]

First --> Because they do what they want.
Second --> Only @AlbertoSONIC was in vacation for 2 weeks, @motezazer for one month.
Third --> Even if they are not on vacation, it means they are working, so I guess they have their priorities, right ?

(Just wait and don't be worry, they will surely return soon...)

Edit : Anyway, the next step is new3DS support.

I can't work alone, because n3ds support is a big thing to add. I need @motezazer ! But I've used last 2 weeks to do more researches for n3ds support, to work on full ninjhax (1.1b) support and especially to learn arm assembly, which is extremely usefull for n3ds support. Also @motezazer has done researches during his vacation, about a *secret* thing. So even if we don't post updates, I can assure you that we're working! Also, I'll have another vacation from tomorrow to August 20th, but I already organized myself to develop during this vacation. I'll go from Italy to Germany and I'll bring with me the laptop and the n3ds!

 

[evandixon]

just a question here guys, the rxtools with pasta devs was in vacation for 2 weeks, its already 2 weeks have passed but why i cant see them posting in this thread about any development or plans?

They've been committing changes to Github, so there's definately progress going on. Something as complicated as this just needs time.

 

[Gadorach]

I tried to downgrade my MSET to 6.x but I get error: Bad Downgrade Pack.

MD5 of msetdg.bin is: 43f6cb581a5c19debd0eee5c003e615d

I get the same MD5 with beta7. Looks like you'll have to downgrade it manually.

USA 0004001000021000 v5128
EUR 0004001000022000 v5127
JPN 0004001000020000 v5127

For 6.X mset^

Sorry, been away working on DSi stuff. If any of you guys are interested, check this out: https://gbatemp.net/threads/dsi-downgrading-the-complete-guide.393682/

Else, for your issues, I triple checked the hash check values. That MD5 is the US 6.x MSET, and it is properly implemented starting with b6, with other fixes up to b8 (and technically b9, for KOR users). Make sure you're selecting the "6.x MSET" option in the downgrader, or that hash will fail. It's dependent on that option being set, as well as your region, to determine if the msetdg.bin is valid for your console. If you're having trouble downgrading MSET, and it's saying it's already exploitable, then try downgrading to another version first, then running the downgrader again with the verison you want to install. This only works on b8+ though, so make sure you're using the latest version.

And to clarify, this is what I mean:

Issue:
Installing 4.x MSET = Already exploitable

Fix:
Install 6.x MSET first, then reinstall 4.x MSET.

Alternatively;

Issue:
Installing 6.x MSET = Already exploitable

Fix:
Install 4.x MSET first, then reinstall 6.x MSET.

All this can be done from the downgrader, from b8+. No need for FBI/BBM.

Oh, and @AlbertoSONIC I was looking through 3DBrew, and I didn't see anything that would let me identify a 2DS specifically to limit MSET installation. Are there any accessible bits from ARM9 that would signify that it was being run from a 2DS? Maybe a special value set on the 3D slider's register? From what I've read though, we can't read that from ARM9, so I'm a bit stuck...

 

[AlbertoSONIC]

Sorry, been away working on DSi stuff. If any of you guys are interested, check this out: https://gbatemp.net/threads/dsi-downgrading-the-complete-guide.393682/

Else, for your issues, I triple checked the hash check values. That MD5 is the US 6.x MSET, and it is properly implemented starting with b6, with other fixes up to b8 (and technically b9, for KOR users). Make sure you're selecting the "6.x MSET" option in the downgrader, or that hash will fail. It's dependent on that option being set, as well as your region, to determine if the msetdg.bin is valid for your console. If you're having trouble downgrading MSET, and it's saying it's already exploitable, then try downgrading to another version first, then running the downgrader again with the verison you want to install. This only works on b8+ though, so make sure you're using the latest version.

And to clarify, this is what I mean:

Issue:
Installing 4.x MSET = Already exploitable

Fix:
Install 6.x MSET first, then reinstall 4.x MSET.

Alternatively;

Issue:
Installing 6.x MSET = Already exploitable

Fix:
Install 4.x MSET first, then reinstall 6.x MSET.

All this can be done from the downgrader, from b8+. No need for FBI/BBM.

Oh, and @AlbertoSONIC I was looking through 3DBrew, and I didn't see anything that would let me identify a 2DS specifically to limit MSET installation. Are there any accessible bits from ARM9 that would signify that it was being run from a 2DS? Maybe a special value set on the 3D slider's register? From what I've read though, we can't read that from ARM9, so I'm a bit stuck...

I don't think we can detect a 2ds because, as you said, arm9 can't do nothing with 3d slider/detection

 

[Gadorach]

I don't think we can detect a 2ds because, as you said, arm9 can't do nothing with 3d slider/detection

Oh well, would've been nice anyway. I'll just add another prompt, or a warning or something. Thanks for the confirm.

 

[gamesquest1]

I don't think we can detect a 2ds because, as you said, arm9 can't do nothing with 3d slider/detection

easiest way around it, if FW is higher than 4.x just use 6.x MSET, no point 5.x+ users having a 4.x MSET really when the 6.x can do its job and not have to worry about 2DS users

 

[Gadorach]

easiest way around it, if FW is higher than 4.x just use 6.x MSET, no point 5.x+ users having a 4.x MSET really when the 6.x can do its job and not have to worry about 2DS users

I've been hearing that 4.x MSET is more stable for higher firmwares though, so until we figure out what's what, I'll probably leave it. Plus, no N3DS ROP for 6.x MSET. Until that's made, that would cause problems for the N3DS support when it arrives, assuming the Gateway 9.x-dg ROP is implemented. Either way, we'll just have to wait and see what happens.

Oh, also, fastboot and autoboot are broken on 6.x MSET. Those should be fixed before 6.x MSET dependence is actually considered.

 

[gamesquest1]

I've been hearing that 4.x MSET is more stable for higher firmwares though, so until we figure out what's what, I'll probably leave it. Plus, no N3DS ROP for 6.x MSET. Until that's made, that would cause problems for the N3DS support when it arrives, assuming the Gateway 9.x-dg ROP is implemented. Either way, we'll just have to wait and see what happens.

yeah, but n3DS should be pretty easy to detect, all im thinking is that for o3DS users who are on 5.x+, there is pretty much no other homebrew designed to run on 5.x+ with the 4.x MSET, so really it would be a good time to ditch it, which would be safer in the long run if 6.x MSET became the new normal

but yeah the only people who have to worry about the 4.x MSET are 2DS users

 

[motezazer]

Status update : my vacations "ended" Sunday, Monday update will be uploaded in a few hours (yes, I'm late).

 

[JJTapia19]

Status update : my vacations "ended" Sunday, Monday update will be uploaded in a few hours (yes, I'm late).

Awesome!!

 

[motezazer]

First --> Because they do what they want.
Second --> Only @AlbertoSONIC was in vacation for 2 weeks, @motezazer for one month.
Third --> Even if they are not on vacation, it means they are working, so I guess they have their priorities, right ?

(Just wait and don't be worry, they will surely return soon...)

Edit : Anyway, the next step is new3DS support.

I was in vacations for two weeks too.

 

[capito27]

Status update : my vacations "ended" Sunday, Monday update will be uploaded in a few hours (yes, I'm late).

As we say in our respective language "Mieux vaut tard que jamais" (= "better late than never", for non french speakers), thanks for your work on porting the tools to N3DS

 

[Gadorach]

So, I feel a tad silly. It should be entirely possible to tell exactly what model a console is by the first few characters of their serial numbers.

For the US it goes like this:

2DS: AW
3DS: CW
3DSXL: SW
N3DSXL: QW

If I had the other regions ID sets as well, it should be possible to identify the console with just the SecureInfo_A data. The only issue is that it wouldn't support region-swapped SysNANDs. I'd have to include an override for them, or find another way to detect them.

 

[happydance]

I've been hearing that 4.x MSET is more stable for higher firmwares though, so until we figure out what's what, I'll probably leave it. Plus, no N3DS ROP for 6.x MSET. Until that's made, that would cause problems for the N3DS support when it arrives, assuming the Gateway 9.x-dg ROP is implemented. Either way, we'll just have to wait and see what happens.

Oh, also, fastboot and autoboot are broken on 6.x MSET. Those should be fixed before 6.x MSET dependence is actually considered.

for me 6.X mset always load the 2nd time after a successful boot...

for example:

Rxtools boots -> Turn off -> DS profile exploit -> Freeze -> Turn off -> DS profile exploit -> Rxtools boots -> Turn off -> DS profile exploit -> Freeze -> repeat

and yes, I've noticed quickboot always give a black screen

 

[DSoryu]

So, I feel a tad silly. It should be entirely possible to tell exactly what model a console is by the first few characters of their serial numbers.

For the US it goes like this:

2DS: AW
3DS: CW
3DSXL: SW
N3DSXL: QW

If I had the other regions ID sets as well, it should be possible to identify the console with just the SecureInfo_A data. The only issue is that it wouldn't support region-swapped SysNANDs. I'd have to include an override for them, or find another way to detect them.

For that you should use warnings or prompts, or maybe something on the title.db could help, there are registers from wich region an app was downloaded if I recall fine (maybe I'm wrong, I's studying various systems right now, it can be from another) (obviously it would not work if anything wasn't downloaded.)

 

[Deleted-19228]

Typo on rxtools.net

http://launch.rxtools.net/rxTools

"You're not using a ninteno 3ds
Visit this page with your nintendo 3ds"

 

[pakrett]

I was in vacations for two weeks too.

Sorry ^^ I remembered one month, I don't know why...