Hacking N3ds 10.3 EMUNAND testing

  • Thread starter Thread starter Toiry921
  • Start date Start date
  • Views Views 27,887
  • Replies Replies 242
  • Likes Likes 3
He's launching rxmode. That means it doesn't matter what firmware he has, it's launching the 9.5 native firm from the SD. That's how rxtools emunand works. But how is 9.5 native firm able to deal with the 10.3 modules in the nand?
 
Last edited by urherenow,
  • Like
Reactions: RednaxelaNnamtra
NATIVE_FIRM runs entirely separately. You can update it in emuNAND all day, every day. What matters is the NATIVE_FIRM used to launch into emuNAND, because that's the one that's going to get used.
Um I might have misunderstood what you said originally, but it sounds like you are implying that even if we somehow installed an updated native_firm and didnt brick our emunand it wouldnt matter because the system is effectively using the 9.0 (or 9.2) one we booted from in sysnand? So games would still read the kernel as being outdated?

--------------------- MERGED ---------------------------

He's launching rxmode. That means it doesn't matter what firmware he has, it's launching the 9.5 native firm from the SD. That's how rxtools emunand works. But how is 9.5 native firm able to deal with the 10.3 modules in the nand?
That's what I thought. So if he somehow got a 10.3 native firm in the emunand it would be launching said native firm which would allow new games to run?
 
Um I might have misunderstood what you said originally, but it sounds like you are implying that even if we somehow installed an updated native_firm and didnt brick our emunand it wouldnt matter because the system is effectively using the 9.0 (or 9.2) one we booted from in sysnand? So games would still read the kernel as being outdated?
No, I'm saying there's two entirely separate things:
  1. The NATIVE_FIRM/firmware.bin used to launch into emuNAND. This is what will be running as NATIVE_FIRM in emuNAND.
  2. The NATIVE_FIRM title installed in emuNAND. This is where title versioning information is pulled from. firm0/firm1 partitions are effectively not used because booting into emuNAND is treated as a warm boot anyway.
That's the extent of my knowledge about firmlaunch at least.
 
I'll rewrite this to try to make sense to it just for the glory of the sun (bold are my notes):
Alright for all of you guys who have been asking for replies: sorry I was overwhelmed by the amount of request and I would rather have given out proof but I wanted to push the videos out quicker to have something to prove it.
1- I had a emunand backup made with emunand9tool (I guess it's a sysnand backup?)
2- I restored nand backup to emunand (I guess he restored sysnand backup to emunand?)
2.5- I then rebooted to check if my games have returned sadly they didn't
3- Then I went back to emunand9 tool then restored the emunand backup when I then went into emunand and a kitten crawled over my system settings launching I realized it was 10.3 rxtools mode.(Magic and things. I do not believe anything of this point)
The downgrade of my 3ds getting got stuck at the 10 seconds screen and I forced reboot after a half hour of waiting. (So looks like a half-downgrade?)

After a good 15 minutes of reading that's the very far I can reach with my english. Looks like a half downgrade did accidental things with emunand9tool. Still I can't understand how that made dbz cart work. Still fishy. lol'd at the kitten.
 
Last edited by Urbanshadow,
Use real rxMode launcher and a fwspoofed .3ds on a Sky3DS.
You can't boot a modded rom on a sky.
Um I might have misunderstood what you said originally, but it sounds like you are implying that even if we somehow installed an updated native_firm and didnt brick our emunand it wouldnt matter because the system is effectively using the 9.0 (or 9.2) one we booted from in sysnand? So games would still read the kernel as being outdated?

--------------------- MERGED ---------------------------


That's what I thought. So if he somehow got a 10.3 native firm in the emunand it would be launching said native firm which would allow new games to run?
No. rxtools loads 9.5 native_firm. period. Just like on a 10.3 o3ds emunand, it's loading the 9.9 native_firm.
 
No, I'm saying there's two entirely separate things:
  1. The NATIVE_FIRM/firmware.bin used to launch into emuNAND. This is what will be running as NATIVE_FIRM in emuNAND.
  2. The NATIVE_FIRM title installed in emuNAND. This is where title versioning information is pulled from. firm0/firm1 partitions are effectively not used because booting into emuNAND is treated as a warm boot anyway.
That's the extent of my knowledge about firmlaunch at least.

So updating native_firm in emunand wouldn't have any real effect then beyond basic compatibility issues with some system titles? As far as exheader kernel checks go, is it checking based on the installed native_firm title or the firmware.bin used to launch emunand?
 
So updating native_firm in emunand wouldn't have any real effect then beyond basic compatibility issues with some system titles? As far as exheader kernel checks go, is it checking based on the installed native_firm title or the firmware.bin used to launch emunand?
I'm not 100% sure, but AFAIK memory is what is checked against, not the title versioning info in the database; don't quote me on it, though. Updating NATIVE_FIRM in emuNAND should do nothing observable whatsoever.
 
I'm not 100% sure, but AFAIK memory is what is checked against, not the title versioning info in the database; don't quote me on it, though. Updating NATIVE_FIRM in emuNAND should do nothing observable whatsoever.

So what exactly causes the blackscreen on update then?

I'm guessing its installing a system title that actually requires the 9.6+ native firm?

Gonna guess this would be the homemenu.
 
The only one who knows how this happened is the kitten, so if OP isn't going to let the kitten do the talking I'm out of here.
bimE5RT.jpg
 
So, we didnt had anything...
Please dont troll with bluemooncard.
Maybe, maybe not.

It did get me thinking so I am gonna try some things of my own and report back. I won't be able to get a full update working, but I MIGHT just be able to get enough of one working to get around the eshop problem and problems with retail carts.

--------------------- MERGED ---------------------------

You have to use something based on make_cdn_cia, it's a python script IIRC

This should be your signature.
I found it.

FW version in title id, region in verison number.

--------------------- MERGED ---------------------------

I won't be able to get a full update working, but I MIGHT just be able to get enough of one working to get around the eshop problem and problems with retail carts.

If anyone is wondering, I suspect we can actually safely install the entire update package minus the homemenu. I suspect the blackscreen is caused by the homemenu derping out when it tries to make calls to native_firm that the old 9.5 one we load from firmware.bin can't respond to.

Edit:

specifically I have seen people talk about installing everything but menu/mint/tiger/mset and I know from personal experience that tiger and mint will not cause problems, and i doubt mset would either since we can downgrade it with no problem.
 
Last edited by Aroth,
been following the thread with interest @Aroth

i think you should create a new thread to detail the progress you make with your theory you have detailed above, i think your defo onto something
 

Site & Scene News

Popular threads in this forum