did they work before trimming?i try normal trim and super trim on new super mario2 and mario land 3D, but when i try both game, they dont work on my Gateway 1.1
What do you mean by not work? And which release where those ROMs?of course yes working great
Sounds to me like NSM2 and marioland 3D are problematic in them selves.NSM2 and marioland 3D was not working for me with 1.0 ... now working great .... with 1.1
mario and luigi dreamland 5.1 too ... amazing .. good job
now mario land 3d trim working ... after 3 try, this time game worked
really nice program ... good work
Are you using command prompt, the program can't be launched by double clicking on it. Put rom_tool.exe in the same directory as your 3DS ROMs and press 'shift' and 'right click' at the same time in the current directory. You have an option to "Open command window here", click on it and it will open a cmd window in your ROM directory. Now you can use rom_tool.I'm having trouble actually starting the trimmer program. I downloaded both the automatic and manual downloads from filetrip but i cant get them to work. I would appreciate the help.
Thanks! Got it to work fine I just also had to rename the rom to Test.3ds for some reason. I just have a simple question: for example the super mario 3d land rom is 512 mb. So if I trim it I'll be able to use it fine, no problem on a 512 mb micro sd card, true? Lol and Its just hard to believe that trimmed roms are exactly the same as untrimmed roms, That is correct I believe?Are you using command prompt, the program can't be launched by double clicking on it. Put rom_tool.exe in the same directory as your 3DS ROMs and press 'shift' and 'right click' at the same time in the current directory. You have an option to "Open command window here", click on it and it will open a cmd window in your ROM directory. Now you can use rom_tool.
http://3dbrew.org/wiki/NCSD
The only way the decrypt the NCCH partitions is with the AES key the NCCH was encrypted with.
No, the keys are stored in two parts(scrambled), one part is known by the 3DS, the other part is calculated from the NCCH header of the NCCH file. Then the two parts are descrambled by a hardware AES engine, and the actual key is written by the AES engine to a register to which only the AES engine can read. So even with kernel level control you won't ever get the final key which is used to decrypt the NCCH.
Great, but you shouldn't have to rename the rom to test.3ds. In regards to your question, yes if you trim it with "rom_tool.exe -t test.3ds" on a 512 mb rom, it should now fit on a 512 mb micro SD card. How well the game runs will depend on the quality and speed of your micro SD card.Thanks! Got it to work fine I just also had to rename the rom to Test.3ds for some reason. I just have a simple question: for example the super mario 3d land rom is 512 mb. So if I trim it I'll be able to use it fine, no problem on a 512 mb micro sd card, true? Lol and Its just hard to believe that trimmed roms are exactly the same as untrimmed roms, That is correct I believe?
When developers create 3DS games, the final ROM is rarely the same size of the chip which it is written to. The chips in 3DS cards aren't made to fit each game which is made, instead game ROMs are written to a chip which is larger than the ROM. 3DS ROM dumps, are dumps of the entire 3DS game card chip, even the unused parts.Lol and Its just hard to believe that trimmed roms are exactly the same as untrimmed roms
WHAT IS "rom_tool" ?
"rom_tool" is a tool I wrote in light of the recently announced Gateway 3DS. It has three main features:
ROM trimming and un-trimming is tested(to trim and un-trim correctly), and works with all 3DS ROM sizes, large(4GB) and small(128MB).
- Read 3DS ROMs, and print information about them, including actual ROM file size, and minimum required 3DS FW etc.
- Accurately trim 3DS ROMs, and be able to restore them again.
- Extract the partitions from 3DS ROMs (and other NCSD Images, such as NAND Dumps)
NOTE: In release v2.6 and onwards, there exists a feature called "Super Trim". This works by removing the update partition(in addition to unused bytes) from the ROM. This has been tested by Devin, and works with Gateway-3DS. However as this is removing used data from the ROM, the removed update partition CANNOT be restored, and the ROM is PERMANENTLY altered. As update partitions are approximately 30MB in size, Super Trimming offers little advantage over regular trimming when dealing with large ROMs. So Super Trimming a ROM should only be done when space is scarce.
NOTE: Super Trimmed ROMs are only compatible with Gateway Version 1.1 and above.
HOW TO USE
This is a command line tool, so you have to use cmd .
View ROM/NAND Dump Info:
rom_tool -i Test.3ds
Extract ROM Partitions:
rom_tool -x <prefix for extracted files> Test.3ds
Trim ROM:
rom_tool -t Test.3ds
Super Trim ROM (Permanently remove update partition):
rom_tool -s Test.3ds
Restore ROM (Untrim):
rom_tool -r Test.3ds
DOWNLOAD(WINDOWS) : FileTrip (v2.7 Released: 23/8/13)
SOURCE CODE : GITHUB
Note the source code was written to be compatible with both Windows and Linux. When compiling on Windows, use MinGW, success not guaranteed with any other Windows developing environment.
That happens because that is an incorrect use of arguments. See the usage details on how to use rom_tool.romtool 2.7
USE command
rom_tool -x test.3ds
Not extracted
That behavior of rom_tool in 2.6 was unintentional. When I extract data I expect to be able to choose the name of output. The behavior of rom_tool 2.7 is aligned with that ideal.Must use the <name>
rom_tool -x <name> text.3ds
but,romtool 2.6
use command
rom_tool -x test.3ds
Can be extracted
Should i update to 4.5.0 or is their no need anymore ?
I'm going to need more information than that to diagnose the problem. Where is the ROM on your computer, where are you running rom_tool from, what is your operating system, is is 32 or 64 bit?I get the following erros when trying to trim from the command line us -t option
[+] Trimming ROM
[!] Invalid File handle
[!] Failed to trim ROM
[!] Failed
-i works fine just seems to be the writing of the file. Admin writes seem fine also.
Any ideas?