Hacking Look this NTR CFW

  • Thread starter Thread starter Timburpton
  • Start date Start date
  • Views Views 82,555
  • Replies Replies 261
  • Likes Likes 1
You can steal it if you don't care about being a thief, but don't share it or use it in your own products.

I will provide a patch of launcher.dat to solve this issue.

Update:
I have removed the Launcher.dat, which is suspected to contains proprietary code.
https://www.sendspace.com/file/vwszrl
 
Excellent solution. For anyone wondering GW's Launcher.dat (as of v1.0) includes ARM11 NATIVE_FIRM Title ID 0004013000001102 at 0x1FF80000. This title is a clean copy of the fs system module http://3dbrew.org/wiki/Title_list from NUS.

Why do that even? Can't you just store a patch and patch at runtime instead of including the whole thing?
 
  • Like
Reactions: Margen67
Thank you Cell9 for that solution :)
No issue sharing your files here now.
I added it to the first post for easy access.

Why do that even? Can't you just store a patch and patch at runtime instead of including the whole thing?
I don't know why they included clean and patched NATIVE_FIRM files. Maybe patching the files in memory is not stable after launching games? or it's faster to load a different file than applying patches at access time. Or the file is not stored in memory. To patch files, they need to be in memory and you patch the memory addresses, you can't patch files while it's been accessed, but you can redirect access to another file (ala riivolution, or like cFW reading files from SD).
Better solution for Gateway would be to let the user extract NATIV_FIM himself from NUS, and patch it if required. But it's not noobfriendly, and they don't care.
 
I don't know why they included clean and patched NATIVE_FIRM files. Maybe patching the files in memory is not stable after launching games? or it's faster to load a different file than applying patches at access time. Or the file is not stored in memory. To patch files, they need to be in memory and you patch the memory addresses, you can't patch files while it's been accessed, but you can redirect access to another file (ala riivolution, or like cFW reading files from SD).
Better solution for Gateway would be to let the user extract NATIV_FIM himself from NUS, and patch it if required. But it's not noobfriendly, and they don't care.

Wait if they have a patched one why even bother including a clean one?
Maybe for classic mode? But then just not patching anything would work.
 
I don't know how it works internally. Other devs decompiled and analyzed it.
I can just guess that some NATIVE_FIRM are clean and other are patched, but I don't know why it includes a clean 4.1 (v7712) when it can read it from NAND. Not for EmuNAND as they need to include corresponding patched FIRM to support EmuNAND on newer version.
 
Edit: Wow, what an arrogant dick I sound like in this post, I guess I was having a bad day. Apologies to piratesephiroth whom I respect as a helpful and knowledgeable member of this community.
Going to leave the original post intact as I'm happy to wear my mistakes.

Also this doesn't make any sense. Reading proprietary file formats is illegal now?
lol it's not the reading that's the issue, it's the (re)packing the data that's the problem. The .cia format is a proprietary format created by Nintendo.

The format is only supposed to be used by developers to aid them in creating software for the 3DS, mostly to make testing and debugging a less painful process.

It's a proprietary format that was developed by, and is owned by Nintendo. The simple fact is we (the public) don't have permission to use it.
 
  • Like
Reactions: Margen67
lol it's not the reading that's the issue, it's the (re)packing the data that's the problem. The .cia format is a proprietary format created by Nintendo.

The format is only supposed to be used by developers to aid them in creating software for the 3DS, mostly to make testing and debugging a less painful process.

It's a proprietary format that was developed by, and is owned by Nintendo. The simple fact is we (the public) don't have permission to use it.

Do we want his CFW for packing CIAs?
 
I don't know how it works internally. Other devs decompiled and analyzed it.
I can just guess that some NATIVE_FIRM are clean and other are patched, but I don't know why it includes a clean 4.1 (v7712) when it can read it from NAND. Not for EmuNAND as they need to include corresponding patched FIRM to support EmuNAND on newer version.

Is there an explanation of how the GW works anywhere.
I thought they just patch the ARM11 kernel. But turns out they patch the fs service. But then...
 
lol it's not the reading that's the issue, it's the (re)packing the data that's the problem. The .cia format is a proprietary format created by Nintendo.

The format is only supposed to be used by developers to aid them in creating software for the 3DS, mostly to make testing and debugging a less painful process.

It's a proprietary format that was developed by, and is owned by Nintendo. The simple fact is we (the public) don't have permission to use it.
Formats won't be restricted unless the developer obtains the patent, at least, in Japan.
 
  • Like
Reactions: Vappy
Yeah, at most, I can see it being illegal to use the official SDK software to pack a .cia, which isn't a problem because we have Makerom.
 
  • Like
Reactions: Margen67
Is there an explanation of how the GW works anywhere.
I thought they just patch the ARM11 kernel. But turns out they patch the fs service. But then...

The entire firmware is all stored twice anyway, second time in SAFE_MODE as backup or an alternative. So yeah they can just replace. For all i know they use the SAFE_MODE files and leave the originals.
 

Site & Scene News

Popular threads in this forum