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

[VerseHell]

About the mset downgrade, is it possible to add a firmware selection in the msetdg.py script?

Like downloading the 6.X mset for 7.0-9.2 and the 4.X one for 5.X.

It will be safer for 2DS users.

 

[Madridi]

Everyone who has issues with QR hacks, should try Devmode boot, it's on Advanced tab.

That's sysnand. The problem is in emunand

 

[Sizednochi]

So I've managed to boot 3.0b5 from 6.X MSET, but no matter what I do I'm getting installation data failed. I've triple checked my firmware.bin, the md5 is a9dcd99a360e8629810f8ed08403d746 as it should be. I don't know what I'm doing wrong as the firmware.bin I have was working fine with 2.6c.

 

[VerseHell]

What is your complete firmware?

 

[Sizednochi]

What is your complete firmware?

As in System firmware? It's 9.2.0-20U if that helps. MSET is 0004001000021000 v5128.

I get the error in both MSET and Spider.

 

[VerseHell]

You can try to install to manually install the patched agb_firm, some people solved the data installation problem like that. I don't know if you havr to install it on emunand or/and sysnand tough.

 

[Sizednochi]

You can try to install to manually install the patched agb_firm, some people solved the data installation problem like that. I don't know if you havr to install it on emunand or/and sysnand tough.

I think that's the problem, thanks for pointing it out.

 

[DSoryu]

That's sysnand. The problem is in emunand

Yes, I know, you need to be on sysNAND 9.X+ though, because emuNAND already patches some exploits or blocks them, @Apache Thunder knows about this much more.

 

[Madridi]

Yes, I know, you need to be on sysNAND 9.X+ though, because emuNAND already patches some exploits or blocks them, @Apache Thunder knows about this much more.

Not everything works in sysnand. Pokémon shuffle for example.

Wait, we are talking about ram hacks yes?

 

[Sizednochi]

So... Nothing works. I tried installing the patched ABG_FIRM, no dice. Reinstalled the clean AGB_FIRM, still hangs at data installation failed.

I don't know why would this happen. 2.6 with 4.x MSET worked fine, even though I get the error I mentioned before from time to time.

It's not just the installation data suite that fails. When I try to boot rxMode in both sysnand and emunand it fails saying "make sure you have all the necessary files in the SD of your console". Like it'd say if firmware.bin wasn't there, which it is.

 

[Apache Thunder]

You probably have the wrong version of the firmware.bin file. How large is the file? it should be around 1.3MB in size roughly. If it's only 940KB in size that is the old one from 2.4/2.5 rxTools. It will not work with newer versions. Redownload the file using cdn_firm.py script (but make sure you use the one from newer versions of rxTools and not the old one). Use the cdn_firm file that came with the version of rxTools you are now using.

 

[Sizednochi]

You probably have the wrong version of the firmware.bin file. How large is the file? it should be around 1.3MB in size roughly. If it's only 940KB in size that is the old one from 2.4/2.5 rxTools. It will not work with newer versions. Redownload the file using cdn_firm.py script (but make sure you use the one from newer versions of rxTools and not the old one). Use the cdn_firm file that came with the version of rxTools you are now using.

That's what I'm using, but the firmware.bin file it generates is 3.4MB, and not 1.3MB. This works with 2.6c.

 

[laramie]

You probably have the wrong version of the firmware.bin file. How large is the file? it should be around 1.3MB in size roughly. If it's only 940KB in size that is the old one from 2.4/2.5 rxTools. It will not work with newer versions. Redownload the file using cdn_firm.py script (but make sure you use the one from newer versions of rxTools and not the old one). Use the cdn_firm file that came with the version of rxTools you are now using.

The firmware.bin recompiles and is named RXfirmware?
EDIT: Never mind, I realized That I didn't have the latest version from github.

 

[Apache Thunder]

Oh your using 2.6c? I think that one does produce a larger firmware.bin. Try the python script from 3.x instead just to see if that works. Which build of rxTools are you using specifically? (from which github fork did you download it from)

The firmware.bin recompiles and is named RXfirmware?

The only version of rxTools that doesn't use the normal firmware.bin name was my fork of rxTools 2.6 with CakeHAX. That one used firmwareRX.bin. However all builds of 3.0 that I had made use firmware.bin like the official builds do.

 

[Sizednochi]

Oh your using 2.6c? I think that one does produce a larger firmware.bin. Try the python script from 3.x instead just to see if that works. Which build of rxTools are you using specifically? (from which github fork did you download it from)

I'm using 3.x from http://jheberg.net/mirrors/rxtools-v30b5/

The firmware.bin file it generates is 3.45mb like I said and it works with 2.6c, but fails to install on 3.x.

 

[Apache Thunder]

Who ever built that may have provided the wrong cdn_firm file. try using the one from the official github page.

 

[Sizednochi]

I'll try it, thanks.

 

[laramie]

Oh your using 2.6c? I think that one does produce a larger firmware.bin. Try the python script from 3.x instead just to see if that works. Which build of rxTools are you using specifically? (from which github fork did you download it from)




The only version of rxTools that doesn't use the normal firmware.bin name was my fork of rxTools 2.6 with CakeHAX. That one used firmwareRX.bin. However all builds of 3.0 that I had made use firmware.bin like the official builds do.

I didn't have the latest version from GitHub... Sorry haha

 

[Apache Thunder]

Ok I was wrong. 3.4MB is the filesize it should be. Your not using the file correctly because it works fine for me. I still think it's perhaps the wrong cdn_firm script you are using.

 

[Sizednochi]

Ok I was wrong. 3.4MB is the filesize it should be. Your not using the file correctly because it works fine for me. I still think it's perhaps the wrong cdn_firm script you are using.

Yeah it generates that file no matter what.
I'm not sure how I'm not using it correctly. You just throw it in the SD root and that's it right? Unless my problem is related to something else. I guess it probably is.

I guess I'll just continue using 2.6c for the time being until an official release is out.

EDIT: Alright, something is wrong here. I put 2.6c back, and it installed data fine. Then I switched the rxTools.dat for the 3.x one - it gives me the error again, but this time booting into rxMode works.

Weird behavior. Well I'll just wait for the official release...