Well there is one way to find out, I could load a o3ds with n3ds files and see what happens. I can't do this immediately though, tomorrow I have PS3's to downgrade and fix. If anyone had one that is bricked already, they could send it in.He could dump the NAND and then replace the o3DS NATIVE_FIRM with the n3DS NATIVE_FIRM, which would be a step in the right direction, but there's still all the o3DS system titles that would almost certainly not load on the n3DS
Well there is one way to find out, I could load a o3ds with n3ds files and see what happens. I can't do this immediately though, tomorrow I have PS3's to downgrade and fix. If anyone had one that is bricked already, they could send it in.
So, the only thing Nintendo has to do right now to prevent that in future software versions, is to release them with NATIVE_FIRM minor version higher than the current one, ie. 2.51?
It's to my understanding it would have to be a pretty major update? That what I've gathered reading various comments.
Kind of. NATIVE_FIRM can be updated to a new Major Version, a new Minor Version, and a new revision. We can only go between revisions, such as 10.5 to 10.2
The home menu is actually universal between regions. Same file is loaded on O3DS/2DS and N3DS.You could if you wanted, but I very much doubt it would help because the home menu CIA is for the n3DS instead of the o3DS. Hard bricked 3DSs probably won't be able to be unbricked until we either have working Arm9LoaderHax or a way to decrypt NAND files. (Don't hold your breath for that second one).
Yea! Because this Exploit automatically installs a Hardmod to their systemWell, this is fantastic! Not only can those who missed the downgrade time do it, but now they get a hardmod out of it.
Yea! Because this Exploit automatically installs a Hardmod to their system
I see the info on U vs J vs E as far as home menu goes, but I don't see anything that says new and old are different.Home Menu has unique title id's per region. So no, Home Menu is not the same for each region. NATIVE_FIRM however is the same for all region consoles as far as I can tell.
Home Menu has unique title id's per region. So no, Home Menu is not the same for each region. NATIVE_FIRM however is the same for all region consoles as far as I can tell.
I see the info on U vs J vs E as far as home menu goes, but I don't see anything that says new and old are different.
Actually, what I said was false. As far as I can tell from https://3dbrew.org/wiki/Home_Menu, the home menu CIA is the same for both n3DS and o3DS. Now I'm wondering how much of the system you need functioning to perform a CUP...
I see the info on U vs J vs E as far as home menu goes, but I don't see anything that says new and old are different.
Exactly. Which is why I said I was wondering how much of the system you'd need to work to get a CUP (Card Update off a game card) to work to then update everything to work properly.It is not different between New and Old at all. Nearest I can tell the guy in question SHOULD be able to get his system to boot in some manner (albeit not fully functional by any means) as long as he can get a proper firm0/firm1 partition injected.
This just got me really hyped omg! I really need a hardmod! To bad they're like 55$ or higher to get a hardmod service
Exactly. I offer different prices depending on the service chosen. There are permanent installs or just downgrade/unbricking services.Contact me, I have 2 different prices. A downgrade only option / and a leave installed option.
Exactly. Which is why I said I was wondering how much of the system you'd need to work to get a CUP (Card Update off a game card) to work to then update everything to work properly.
Well, considering that it looks like most of the system modules I listed earlier (GSP, MCU, i2s, PTM and spi, specifically) are what handle memory mapping and reading/writing from the various registries (at least from what I am seeing on 3dbrew) I think he is probably fucked. It wouldn't hurt to try and if he get can at least get the home menu to load then he MIGHT be able to use a CUP or even access system settings and update that way (actually he would need to in order to fix several N3DS unique files that are only touched by NUPs, like NVer and the browser).
That said I strongly suspect that even if he got the right data in firm0/firm1, his system would still fail to load since it seems those N3DS unique modules would be needed to properly access the cpu and memory. Make sense to considering the N3DS has a faster cpu with larger registers and more ram, all of which would not be properly mapped or accessed by O3DS versions of those modules.