Hello, someone who doesnt understand what im doing here. I tried to use the 3ds cia converter but it just responds with wrong xorpad. Im using decrypted roms downloaded from the web with godmode9
You could just do "ctrtool --contents=contents game.cia" Or if you're not familiar with command line tools you can google "Asia81HackPack" and use that to extract the CIA.
My CIA file fails to install and I don't know why. I followed the instructions using xorpad files and I received the message in the pic provided. Now I'm starting over and I'm trying to use the new version 5.0 method with the boot9.bin file to create a new CIA file, and I get the error message that I need to generate my xorpads. I have a few questions:
1) In which folder do I put the boot9.bin and *.3ds files exactly?
2) Do I still need to create the ncchinfo.bin file if I no longer need the .xorpad files?
3) How do I know if I have the proper key to use the boot9.bin file? I just dumped my boot9.bin file to my boot9strap folder and I'm using that (date modified is 5/1/2017).
1) In which folder do I put the boot9.bin and *.3ds files exactly?
2) Do I still need to create the ncchinfo.bin file if I no longer need the .xorpad files?
3) How do I know if I have the proper key to use the boot9.bin file? I just dumped my boot9.bin file to my boot9strap folder and I'm using that (date modified is 5/1/2017).
Attachments
Last edited by Chomper,
Use 3dsconv, it's 2x even 3x faster (from personnal use), no need to generate xorpads, and you have a percentage display.Hope to display a progress bar when converting multiple filesThanks.
Just drag'n'drop your .3ds and you're done.
Last edited by Asia81,
I just gave this a shot (just got Luma set up on my 3DS) and after installing the .cia with FBI it tells me I have a new title and is listed, but when I try to Unwrap nothing happens. These are the steps I did:
**EDIT** sigh, again--disregard. Just needed to restart the device and they opened fine. :/
- Extracted Simple CIA Converter to folder on desktop and launched it. Saw folders were created.
- Copied boot9.bin from /boot9strap folder of SD card to Simple CIA Converter folder on desktop.
- Copied .3DS file (Dragon Quest VII) into Simple CIA Converter's /roms subfolder.
- Launched Simple CIA Converter.
- Clicked Create 'ncchinfo.bin', though I'm not sure this is needed anymore in new version?.
- Clicked Convert 3DS ROM to CIA and pointed it at folder where .3ds file is located.
- Once it was complete, copied the .cia file to SD card in /cias.
- Inserted SD into 3DS and booted up.
- Launched FBI installer.
- Browsed to the dq7.cia file and installed it.
- Shaved my beard, regrew it, raised a family.
- When it was done I exited FBI installer and saw Dragon Quest VII listed as a new item on the screen, but could not unwrap it.
**EDIT** sigh, again--disregard. Just needed to restart the device and they opened fine. :/
Last edited by midas1108,
hi guys and thanks Riku for this... i hope someone can help me with my issue.
i have pre decrypted .3ds files and i cannot convert them to .cia no matter what i tried.. decypting them doesnt make sense anyway since they are decrypted already .. any ideas?
i have pre decrypted .3ds files and i cannot convert them to .cia no matter what i tried.. decypting them doesnt make sense anyway since they are decrypted already .. any ideas?
In case the readme.txt was not very clear about where to place the 'boot9.bin' file, it goes in the main '3DS Simple CIA Converter v5.0' folder and not in the 'xorpads' subfolder. You do not need to place a second 'boot9.bin' in 'xorpads'. You also do not need to Create 'ncchinfo.bin' file beforehand; this step is redundant. Just go straight to Convert 3DS ROM to CIA after once you have the 'boot9.bin' & placing your 3DS files in the 'ROM' folder.
Another thing I found out is that you do not have to worry about extracting different boot9.bin files from separate 3DS systems. They're the exact same file as far as I could tell using winRAR to check CRC32 hash between both of my New 3DS units. I dunno if differences in firmware create different boot9.bin, but both of mine are on 11.6-0.39U firmware.
Edit : More clarification. You only need to extract just the 'boot9.bin' file and not the 'boot11.bin'. To create boot9.bin, press and hold the (Start) + (Select) + (X) buttons for a few seconds at start up when turning on your 3DS. If you keep holding this combination, you will be stuck at a blank screen. This is fine. Just let go of the buttons to enter into 3DS Home Menu. Restart the 3DS while holding (Start) to enter Luma Chainloader. Select GodMode9, go to SDCARD > boot9strap folder to check if 'boot9.bin' , 'boot11.bin' , and 'otp.bin' were created. This might take several attempts and restarts if these don't show up. You can delete these three after obtaining boot9.bin.
Another thing I found out is that you do not have to worry about extracting different boot9.bin files from separate 3DS systems. They're the exact same file as far as I could tell using winRAR to check CRC32 hash between both of my New 3DS units. I dunno if differences in firmware create different boot9.bin, but both of mine are on 11.6-0.39U firmware.
Edit : More clarification. You only need to extract just the 'boot9.bin' file and not the 'boot11.bin'. To create boot9.bin, press and hold the (Start) + (Select) + (X) buttons for a few seconds at start up when turning on your 3DS. If you keep holding this combination, you will be stuck at a blank screen. This is fine. Just let go of the buttons to enter into 3DS Home Menu. Restart the 3DS while holding (Start) to enter Luma Chainloader. Select GodMode9, go to SDCARD > boot9strap folder to check if 'boot9.bin' , 'boot11.bin' , and 'otp.bin' were created. This might take several attempts and restarts if these don't show up. You can delete these three after obtaining boot9.bin.
Last edited by TurdPooCharger,
the bootrom is burned into the cpu at the factory. it is identical for all produced systems (new/old, retail/dev). it cannot be updated without a hardware revision, which is too expensive and not worth it this late in the console's life.
only dumping is the suggested method for copyright reasons. getting it via other means is piracy and not supported here.
In case you can't or won't extract your own boot9.bin, the CRC32 hash for this file is E0989F6D.
Wait if I convert my legit .3ds game (dumped) to .cia would It be compatible with the legit eshop application and the updates from eshop? I mean, "fake" .cia or legit/good .cia (eshop compatibility)?
Updates aren't done on eShop but through launching the game needing an update and pressing Y. (I believe) DLC for the games are tricky as Nintendo eShop will know you didn't purchase those if you did not buy and install them through eShop, and these will get deleted off your 3DS. Just don't go on eShop and stick to the alternative.
hmm I remember installing some .cias (games) and after that i entered the legit eshop application to update the games and I got an error or something like that and I was able to repair the game and to update it aswell. I guess it was a "bad/fake" .cia and I repaired it using the legit eshop application. Now, I dont know if this would still work with newer games/firmwares.
Last edited by deSSy2724,
Similar threads
