Hacking Version 1.10?!

[DjoeN]

you will need Cubic Ninja to do this though since there's no browser (until 2.0.0-2)

And lucky enough, Cubic Ninja only needs FW 1.0 to work
BUT
The only problem, there's no payload for CN below 4.0

[EDIT]

There's a CN qr for 1.x. once otp is achieved cart update to 4.x or 9.x

Ow is there?

 

[ihaveahax]

And lucky enough, Cubic Ninja only needs FW 1.0 to work
BUT
The only problem, there's no payload for CN below 4.0

but the payload used isn't ninjhax, it's a custom one purely for dumping OTP.

 

[dkabot]

but the payload used isn't ninjhax, it's a custom one purely for dumping OTP.

Can confirm, this is why the OTP guide has CN and Spider versions.

 

[lostreverie]

I appreciate all the advice. Please forgive me if I'm a little confused--I'm a bit behind the 3DS scene. I've only hacked two devices, and I was fine living the MenuHax life in both cases.

It sounds like I can send the device to hundshamer to get it hardmodded. Does this cost me money? Or does the contribution of the firmware dump cover it? I would be happy to contribute to the community if doing this would help development. But what exactly does hardmodding the device allow it to do?

I don't have any way of upgrading to 2.1 (I have a 2.2 cart). Does hardmodding it solve that problem? Or could I install A9LH on 2.2?

Lastly, what does A9LH allow me to do that I could not do through just browserhax/menuhax? Having read through the compile/installation guide, I'm confident it's not beyond my level, but I'm having trouble understanding the purpose of such a comparatively complex procedure. Why dump the OTP.bin and install A9LH instead of using a gamecard to update and going through the browser/menuhax procedures?

 

[dkabot]

I appreciate all the advice. Please forgive me if I'm a little confused--I'm a bit behind the 3DS scene. I've only hacked two devices, and I was fine living the MenuHax life in both cases.

It sounds like I can send the device to hundshamer to get it hardmodded. Does this cost me money? Or does the contribution of the firmware dump cover it? I would be happy to contribute to the community if doing this would help development. But what exactly does hardmodding the device allow it to do?

I don't have any way of upgrading to 2.1 (I have a 2.2 cart). Does hardmodding it solve that problem? Or could I install A9LH on 2.2?

Lastly, what does A9LH allow me to do that I could not do through just browserhax/menuhax? Having read through the compile/installation guide, I'm confident it's not beyond my level, but I'm having trouble understanding the purpose of such a comparatively complex procedure. Why dump the OTP.bin and install A9LH instead of using a gamecard to update and going through the browser/menuhax procedures?

Hardmods aren't like modchips or anything; they're just a direct hookup of the NAND to an adapter (because the NAND is basically an embedded SD card) which allows for dumping it externally.
Since there's no exploits set up for 1.0 to allow such a dump in software, a hardmod is basically needed for this (alongside its added safety for experimentation).
Whether someone covers the cost is unknown, at least on my end. Not sure there's really a huge demand for 1.0 dumps aside from people who say these things.

Technically, you don't go to 2.X to install A9LH, but to get a value from the OTP, which was patched for good in 3.0 (and why people downgrade).
After getting the OTP, you'd need to compile/get someone to compile A9LH and run it from probably 9.2 to actually install it.

A9LH is ARM9 control at boot, earlier than even MenuHax.
This allows for a fix to the N3DS 3D bug (irrelevant here), faster boot times, a 100% boot rate, the ability to use a hax'd environment without EmuNAND (though it's recommended to have of 9.2 if this is done) and potential brick protection (as you can basically always restore so long as FIRM0/1 are safe). Also, it's new tech and thus having it makes you

 

[lostreverie]

Hardmods aren't like modchips or anything; they're just a direct hookup of the NAND to an adapter (because the NAND is basically an embedded SD card) which allows for dumping it externally.
Since there's no exploits set up for 1.0 to allow such a dump in software, a hardmod is basically needed for this (alongside its added safety for experimentation).
Whether someone covers the cost is unknown, at least on my end. Not sure there's really a huge demand for 1.0 dumps aside from people who say these things.

Technically, you don't go to 2.X to install A9LH, but to get a value from the OTP, which was patched for good in 3.0 (and why people downgrade).
After getting the OTP, you'd need to compile/get someone to compile A9LH and run it from probably 9.2 to actually install it.

A9LH is ARM9 control at boot, earlier than even MenuHax.
This allows for a fix to the N3DS 3D bug (irrelevant here), faster boot times, a 100% boot rate, the ability to use a hax'd environment without EmuNAND (though it's recommended to have of 9.2 if this is done) and potential brick protection (as you can basically always restore so long as FIRM0/1 are safe). Also, it's new tech and thus having it makes you

Thanks so much for this simple explanation. Now that I actually know what I'm doing, I should be able to start figuring out how to do it!