search

hacks-guide / Guide_3DS

A complete guide to 3DS custom firmware, from stock to boot9strap.
https://3ds.hacks.guide/
MIT License
1.57k stars 315 forks source link

A minor note about emu/redNAND creation with the new guide #394

Closed jaxrogers2 closed 8 years ago

jaxrogers2 commented 8 years ago

The new ctrtransfer guide is amazing! But as I was looking over it, there is only one slight problem. If somebody started at a lower firmware (such as 4.X, 6.X, etc.) and then did the ctrtransfer through Decrypt9 to downgrade to 2.1 and get A9LH, that means that they will never be able to create an emu/redNAND in the future because the backup that they have (created before the transfer) is for that lower firmware, which (if it is low enough) will not boot on an emu/redNAND. And since flashing sysNAND to emu/redNAND with A9LH installed also makes the emu/redNAND unbootable, that means that those users are simply out of luck. In order to fix this, the guide should direct people at these low firmwares that cannot be booted in CFW red/emuNAND to update to a firmware that will boot in an emu/redNAND and then perform the ctrtransfer. However, since an emu/redNAND is entirely optional when A9LH is installed, this process should be optional also.

Plailect commented 8 years ago

This is because of an issue in the way d9 stores the NCSD header backups in ctrtransfer systems and how Luma3DS boots traditional EmuNAND. This issue does not affect RedNANDs, and should be fixed soon.

For now, creating a RedNAND from SysNAND using EmuNAND9 then booting it with Luma will work.

arromdee commented 8 years ago

It sounds like this issue still would legitimately arise for 2.1.0-4 since the procedure for that doesn't involve a cart update and Luma can't boot 2.1 with or without a d9 fix.

pixel-stuck commented 8 years ago

At this point, we do a ctrtransfer to 9.2, then make an emuNAND from the resulting image

On Thu, Aug 25, 2016, 5:19 PM arromdee notifications@github.com wrote:

It sounds like this issue still would legitimately arise for 2.1.0-4 since the procedure for that doesn't involve a cart update and Luma can't boot 2.1 with or without a d9 fix.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Plailect/Guide/issues/394#issuecomment-242544115, or mute the thread https://github.com/notifications/unsubscribe-auth/ADd1uBEnlr9WzSskT74MSGVe1x6EtMRiks5qjgbsgaJpZM4JtNOA .