Homebrew O3DS firmware on n3DS?

[Ironknight]

Hello there, I have a n3DS XL with an updated sysnand with A9LH and luma, and in the 2.1 downgrade the OTP helper patched the o3DS firmware to work on a n3DS. I wanted to know if I can create an emuNAND, downgrade it to 10.7 or something, and update it (with sysupdater) to o3DS 11.0, and then patch it to work on my n3DS? Because I know that you cant system transfer from a n3DS to an o3DS, but a friend of me got a o3DS on ver. 11.0, so I really want to trick the other 3DS into thinking I have an o3DS. Thanks in advance!

 

[Deleted member 366698]

Nope, that won't work in any way.
The way the nand works between consoles is very different .
Don't even try such.
Just follow the guide each time for each console, it's not that hard

 

[Ironknight]

Nope, that won't work in any way.
The way the nand works between consoles is very different .
Don't even try such.
Just follow the guide each time for each console, it's not that hard

I dont think you understand. I have a New 3DS. My friend has a Okd 3DS. If I cant get an old 3DS firmware to work on my emuNAND, I cant transfer the DSiHax, and thus cant downgrade HIS old 3DS.

 

[Gray_Jack]

Hello there, I have a n3DS XL with an updated sysnand with A9LH and luma, and in the 2.1 downgrade the OTP helper patched the o3DS firmware to work on a n3DS. I wanted to know if I can create an emuNAND, downgrade it to 10.7 or something, and update it (with sysupdater) to o3DS 11.0, and then patch it to work on my n3DS? Because I know that you cant system transfer from a n3DS to an o3DS, but a friend of me got a o3DS on ver. 11.0, so I really want to trick the other 3DS into thinking I have an o3DS. Thanks in advance!

Well... in theory... yes... But I don't think you should do that or try to do that

 

[Ironknight]

Well... in theory... yes... But I don't think you should do that or try to do that

But if I dont try it, how can I transfer the DSihaxed fieldrunners from my n3DS to his o3DS. Because I cant. I need to have an o3DS firmware as my emuNAND to transfer.

 

[Gray_Jack]

Btw, no one did it, so don't even try if you don't know what are you doing

 

[Ironknight]

Btw, no one did it, so don't even try if you don't know what are you doing

I dont know what I am doing, thats why I am asking. The OTPHelper had a feature that did it automatically, and I think now that 11 is downgradable via fieldrunner, a standalone program that does that would be helpful for many people.

 

[Gray_Jack]

But if I dont try it, how can I transfer the DSihaxed fieldrunners from my n3DS to his o3DS. Because I cant. I need to have an o3DS firmware as my emuNAND to transfer.

So try it, try to encounter a very old version version of the plailect guide that we had to patch the 2.1 emuNAND backup and patch it to work on N3DS and do it with the Old 11.0 emuNAND
You will probably get a brick that you cannot recover from

 

[Ironknight]

So try it, try to encounter a very old version version of the plailect guide that we had to patch the 2.1 emuNAND backup and patch it to work on N3DS and do it with the Old 11.0 emuNAND
You will probably get a brick that you cannot recover from

As if I use my sysnand for that shit. I would use an unlinked emunand. And because it will be 11, I could boot it with a cfw instead of having to flash it to sysnand. As long as I dont touch my sysnand Firm1 and Firm0, everything is okay.

 

[Gray_Jack]

As if I use my sysnand for that shit. I would use an unlinked emunand. And because it will be 11, I could boot it with a cfw instead of having to flash it to sysnand. As long as I dont touch my sysnand Firm1 and Firm0, everything is okay.

Ok, not my problem man, but be aware that even the oldest method to patch was made oly for 2.1, if it work... well... awesome, let me know. If don't... please don't start calling me inappropriate names

 

[Temarile]

You probably just end up bricking maybe even both devices, but if you want to risk that, go ahead and try. ¯\_(ツ)_/¯

 

[nero99]

You probably just end up bricking maybe even both devices, but if you want to risk that, go ahead and try. ¯\_(ツ)_/¯

How could he brick the other device without touching it's NAND?

 

[Temarile]

How could he brick the other device without touching it's NAND?

The NAND from the N3DS is severely different from the NAND. He's transferring from N3DS -> O3DS, which was never made possible by Nintendo because of these differences. Assuming the transfer succeeds, the N3DS NAND would be on a O3DS which can't handle the N3DS NAND, thus possibly bricking it. Just a guess though, as noone ever tried this.

 

[nero99]

The NAND from the N3DS is severely different from the NAND. He's transferring from N3DS -> O3DS, which was never made possible by Nintendo because of these differences. Assuming the transfer succeeds, the N3DS NAND would be on a O3DS which can't handle the N3DS NAND, thus possibly bricking it. Just a guess though, as noone ever tried this.

This sounds fun. But doesn't system transfer only transfer your encrypted titles and NNID and not the entire NAND?

 

[Gray_Jack]

The NAND from the N3DS is severely different from the NAND. He's transferring from N3DS -> O3DS, which was never made possible by Nintendo because of these differences. Assuming the transfer succeeds, the N3DS NAND would be on a O3DS which can't handle the N3DS NAND, thus possibly bricking it. Just a guess though, as noone ever tried this.

I don't think the system transfer transfer the NAND... I think it just send the needed and proper signed things to the other 3DS + account data
Nintendo probably made O3DS to N3DS possible and N3DS to O3DS impossible because the system transfer would try to pass even the N3DS only games (that don't supposed to be installed on O3DS)

 

[TimX24968B]

i thought he was trying to essentially make a version of o3ds firmware on his n3ds and try to do some sort of system transfer (or something of the like). THAT looks like it would take alot more research, and figuring out a way to make o3ds firmware work on a n3ds in some way.

 

[Ironknight]

i thought he was trying to essentially make a version of o3ds firmware on his n3ds and try to do some sort of system transfer (or something of the like). THAT looks like it would take alot more research, and figuring out a way to make o3ds firmware work on a n3ds in some way.

I thought of a tool that creates an emuNAND, installs o3DS 11.0, and then patches it, so that people with a n3DS can transfer their fieldrunner with hax installed to an o3DS. That would be VERY useful for everyone with a n3DS, that has friends on 11.0 with an o3DS.

 

[davidlc]

I thought of a tool that creates an emuNAND, installs o3DS 11.0, and then patches it, so that people with a n3DS can transfer their fieldrunner with hax installed to an o3DS. That would be VERY useful for everyone with a n3DS, that has friends on 11.0 with an o3DS.

You just thought of the idea, that's the easy part. If you want people to actually code some sort of solution for that, you're better off trying to find a o3DS or a 2DS from a friend, because nobody seems to be developing such tool.

 

[TimX24968B]

I thought of a tool that creates an emuNAND, installs o3DS 11.0, and then patches it, so that people with a n3DS can transfer their fieldrunner with hax installed to an o3DS. That would be VERY useful for everyone with a n3DS, that has friends on 11.0 with an o3DS.

good luck getting a n3ds to run o3ds firmware. thats all i have to say

 

[Oishikatta]

good luck getting a n3ds to run o3ds firmware. thats all i have to say

Isn't that exactly what is done when retrieving the OTP? N3DS never had a 2.x firmware.