Hacking [Tutorial] 4.5 SysNAND + 4.5 CFW + 9.4 EmuNAND without Gateway

  • Thread starter Thread starter Chaldron
  • Start date Start date
  • Views Views 272,846
  • Replies Replies 773
  • Likes Likes 28
after a few weeks of using cfw, o got alot of crash, in the firmware and also in game. is it normal? how can i solve it?
 
How would I do that, I'm not that great with partitioning stuff.


Once you've copied the contents of the SD card over, you'd just need to run any partition management software. Then select the partition on your SD card and resize it to fill the whole SD card afterwards (but not the 1GB at the front, that's your emunand)
 
I successfully downgraded from 9.0 to 4.5 without Gateway.
I have some eshop games on SD card: mariokart7, dream team bros, Zelda Ocarina, Zelda A Link Between Worlds, RE, Tetris, some DSi games.
After downgrading ALL eshop stuff works - EXCEPT one game that I really need: Zelda A Link Between Worlds. When I try to load it, 3DS says something like "SD card was removed, press home to return to home menu" - and that's it. :(
Is there any way to make this particular eshop game work as it was before downgrade?..

Don't have GW.
Don't have DS flashcard (yet). (Waiting for Blue GW card).
All stuff from SD card is backup-ed on PC.
9.0 NAND.bin also backup-ed, of course.

Please help...
 
I heard that you could run Bangai-O-Spirits (U) and run the DS Mode exploit that way, could anybody confirm this please? (I've already downgraded my system to 4.2.0)
 
Nonono, it's not that. Smealum was trying things left and right when he stumbled upon Bangai-O-Spirits (U) (which is a ds game btw) and he realised he could hack it to run ds programs, this has nothing to do with hacking the 3DS.
Here is a vid he posted.

 
If I install an EUR .cia in my USA 3DS with devmenu in CFW, will be a problem?

Thanks in advance (:


What do you think????? Of course you'll have an issue....usa cia's or region free converts (usa or eur...doesn't matter)
 
I managed to have on my 4.x 3DS two emunand on the same SD, one to be launched with MT loader and updated to last FW so you can go online or on eshop, the other for the CFW emunand to run CIAs and Homebrew.

For me it was an experiment after completing the RE of the CFW part that boots the emunand. Really don't know if it's worth to have two emunand on the same SD or if it's better to have two SD to swap when you need it.

The only little benefit is that you don't have to pul off the sd if you use the launcher.dat file for MT and the msetforboss.dat file for the CFW. You can simply swap the used launcher with the multiroploader on the SD cart. This may help to save your Sd slot.

I can make I tutorial, but only if it is of any interest to some members of the forum.

Let me know.
 
I managed to have on my 4.x 3DS two emunand on the same SD, one to be launched with MT loader and updated to last FW so you can go online or on eshop, the other for the CFW emunand to run CIAs and Homebrew.

For me it was an experiment after completing the RE of the CFW part that boots the emunand. Really don't know if it's worth to have two emunand on the same SD or if it's better to have two SD to swap when you need it.

The only little benefit is that you don't have to pul off the sd if you use the launcher.dat file for MT and the msetforboss.dat file for the CFW. You can simply swap the used launcher with the multiroploader on the SD cart. This may help to save your Sd slot.

I can make I tutorial, but only if it is of any interest to some members of the forum.

Let me know.
I would like to know how have you done that :)
 
I would like to know how have you done that :)

It's some weeks that in the WE free time I'm RE the CFW.

To redirect the sysnand to the SD the read/write functions are patched to be redirected to some custom code that change the device from firm to sdmc and simply add or subtract the sector offset to the nand phisical address to be read/write.

The offset is a four byte value placed at position 0x14 in the file boot.bin (01 00 00 00 in little endian, that means 0x00000001 = 1 sector offset).

If you change this value in 0x00200001 with an hex editor (you have to change the 00 at 0x16 in 20) the loader will point to an emunand placed after the MT emunand.

At this point you have to enlarge the hidden partition from 1GB to 2GB (with gparted or with diskpart on windows) and then inject the CFW emunand starting from sector 0x00200001 using dd or something similar under windows (I use bbcopy).

Very easy if you can use low level tools like an hexeditor, a partition tool and dd.

For a less experienced user I could write a step to step tutorial, because playing with partitions or with dd can be very dangerous if you select the wrong disk.
 

Site & Scene News

Popular threads in this forum