Homebrew ARM9Loader -- Technical Details and Discussion

  • Thread starter Thread starter Selver
  • Start date Start date
  • Views Views 579,205
  • Replies Replies 4,025
  • Likes Likes 42
I dunno if it helps but I just noticed that "https://plailect.github.io/OTP/" guide includes n3ds(E) pack with a windows.py script which uses nand.fat16.xorpad instead of nand.fat16_0x5_.xorpad. Also includes "NCSD_header_o3ds.bin" I dunno if ncsd should be for n3ds instead.
I think the correct command should be like this
"3DSFAT16tool.exe -d -n emuNAND_bricked.bin ctr.bin nand.fat16_0x5_.xorpad
3DSFAT16tool.exe -i -o emuNAND_bricked.bin ctr.bin nand.fat16_0x4_.xorpad"
Good thing a backed out. Can anyone confirm that the script is faulty?
No, the NCSD must be for O3DS, to make it think it's a O3DS, because 2.1.0-4E doesn't exist for N3DS.

And IIRC, it was changed because Decrypt9 names the 0x4 xorpad nand.fat16.0x4.xorpad now
 
No, the NCSD must be for O3DS, to make it think it's a O3DS, because 2.1.0-4E doesn't exist for N3DS.

And IIRC, it was changed because Decrypt9 names the 0x4 xorpad nand.fat16.0x4.xorpad now
About NCSD just as I thought. Also the same goes for wifi, it must be left turned on in emunand just because n3ds doesn't have wifi slider, right?
I just re-read the first section of "that otp guide" and they changed a few things. So the "_0x5_" is now removed, and it's just nand.fat16.xorpad while "_0x4_" is renamed to 0x4.
Thanks for clearing things out.
 
  • Like
Reactions: Mrrraou
About NCSD just as I thought. Also the same goes for wifi, it must be left turned on in emunand just because n3ds doesn't have wifi slider, right?
I just re-read the first section of "that otp guide" and they changed a few things. So the "_0x5_" is now removed, and it's just nand.fat16.xorpad while "_0x4_" is renamed to 0x4.
Thanks for clearing things out.
Inconsistencies are great aren't they? haha
And yeah the wifi, sadly nintendo are cheap asses and didn't put a bloody hardware wifi switch on n3ds :(
 
What if I wanted to lets say keep bricked nand rom of 2.1.
I just have to delete "os.system('del ctr.bin')" from python script or change "os.system('move emuNAND_bricked.bin " to "copy emuNAND_bricked.bin", which one XD?
 
Last edited by LooneyElsa,
I have a quick question, on reinand mod I hear for people who want to have their emunand stuff on sysnand they have to downgrade emunand to 9.2, make a backup of it and transfer that backup over sysnand, afterwards needing to reinstall a9lh. Why would you need to reinstall a9lh though?
 
I have a quick question, on reinand mod I hear for people who want to have their emunand stuff on sysnand they have to downgrade emunand to 9.2, make a backup of it and transfer that backup over sysnand, afterwards needing to reinstall a9lh. Why would you need to reinstall a9lh though?
They are doing it wrong. They just have to take the emuNAND CTRNAND and putting it on sysNAND (backup your sysNAND CTRNAND first!). Then they can use the updated sysNAND mod from Aurora's mod, and they'll have all their emuNAND stuff on sysNAND.
 

Site & Scene News

Popular threads in this forum