d0k3 / emunand9 Goto Github PK

Since boot9strap is incompatible with the .bin version of EmuNAND9, I decided to use the .nds version with my flashcart instead. My concern here is that when I entered the .nds version of EmuNAND9, I arrived at a menu that includes : >>Cakes ROP Installer<< as the title.

I pressed A on the 4.x EmuNAND9 option and something happened and then my console rebooted. Did I somehow fuck something up? I really need to know what happened because I am a bit paranoid right now.

I have boot9strap v1.2 and Luma3DS v7.0.5 btw.

I know that EmuNAND9 is discontinued technically, but its user friendliness in making redNANDs and Gateway-type EmuNANDs is what makes it appealing over Godmode9. Could you find it in your heart to make just one more release for boot9strap since B9S doesn't support .bin files?

You did so for hourglass9, so I thought it wouldn't be too much to ask to make the same request for EmuNAND9.

Is it possible support Multi EmuNAND Create
add blew function
Multi EmuNAND Options
Format Multi EmuNAND 2/3/4
Clone your SysNAND to EmuNAND1 / RedNAND1
Clone your SysNAND to EmuNAND2 / RedNAND2
Clone your SysNAND to EmuNAND3 / RedNAND3
Clone your SysNAND to EmuNAND4 / RedNAND4
Backup your EmuNAND1 / RedNAND1 to a file
Backup your EmuNAND2 / RedNAND2 to a file
Backup your EmuNAND3 / RedNAND3 to a file
Backup your EmuNAND4 / RedNAND4 to a file
Restore your EmuNAND1 / RedNAND1 from a backup
Restore your EmuNAND2 / RedNAND2 from a backup
Restore your EmuNAND3 / RedNAND3 from a backup
Restore your EmuNAND4 / RedNAND4 from a backup
Convert your EmuNAND1/2/3/4 -> RedNAND1/2/3/4 or vice versa

Hi,
im trying to hack my 3ds with this Guide : https://github.com/Plailect/Guide/wiki
Part 3 - RedNAND

but some i cant go further then step 7/10 (Complete RedNAND setup) - if im entering that option and pressing "A" to start it, nothing happens...

anyone has an idea?

[https://abload.de/img/imagev0odq.jpeg]
[https://abload.de/img/imagey3uee.jpeg]

Hi guys,

I encouter a major bug with EmuNAND9 on all last versions.

I can't navigate with the d-pad. If I click 'down' the line come back directly at the first position.
It's possible to navigate by holding 'down' and 'right' or 'left' buttons. but impossible to pass the sequential test '

It's very strange, I just encouter this problem on emunand. I try all the last versions with a fresh starter pack, format the console etc. I'm on 9.2.0.20.E

It's possible to have a version with analog pad supported ? regards

i use EmuNAND9(20160201) to backup nand, there is no .sha file and otphelper can not recognize it's header. can i restore nand without EmuNAND9(20160201)?

There's a case to be made for 64KB Cluster Size, but there's a known issue with GBA games where the screen gets wrapped improperly for some reason, especially on larger (and therefore slower) SD cards.

Changing the cluster size to 32KB instead of 64KB seems to entirely fix this issue, and since a lot of people use EmuNAND9 to format their cards, it'd be wise to revert back to 32KB instead.

Relevant issues from other repos:
LumaTeam/Luma3DS#142

After using, EmuNAND9 format EmuNAND partition size is 1.2GB
But Gateway format EmuNAND partition size is 2GB
So, whether EmuNAND9 partition is NOT enough for future EmuNAND system update ???

Commit 840c7e1 added an MBR entry for the EmuNAND partition, which is a good idea overall. However, some OSes may show the drive as "unformatted", which may lead to an accidental format as FAT32, thus destroying the EmuNAND.

Instead of partition type 0x0C, consider using type 0x1C. This is used by various recovery partitions to indicate a "hidden" FAT32 partition, so Windows won't try mounting it as a regular drive.

Reference: https://en.wikipedia.org/wiki/Partition_type

Luma3DS's emuNAND/redNAND detection looks for a magic string in the image to identify things, not the partition table. The quick format option to remove an emunand will leave this on the SD card even though the emuNAND has been corrupted, and can cause ARM9 exceptions on boot.

I know this is really a Luma3DS problem, and they should be checking the partition table to see if space is reserved, but could you have this wipe those blocks while reformatting just to avoid the trouble?

-Ken

It says the SD card is not ready but I have enough space to fit it in and I formated it

This was noticed with a (o3DS) 10.3 EmuNAND backup made with latest rxTools.

Trying to restore it with EmuNAND9 will output this error : "NAND dump has the wrong size!"
However, restoring it with EmuNAND tool on a Windows system worked.

The backup is ~988Mo/7910Mb.

New A9LH 2.0 broke all the .bin payloads using 1.X, so in order for people who have installed V2.0 of A9LH already this needs to be updated.

Self explanitory.

Sorry this isn't much of a issue, I just wanted confirmation from the actual maker of the software so please forgive me if I'm doing something wrong.

Not really an issue but more like a couple of questions:

1. If I convert my current EMUNand to REDNand will it free up space on the useable partition?
2. Wil I have to recopy anything if I convert my current EMUNand?
3. Will I retain the current installed CIAs when I convert?
4. How much space difference am I to expect when I convert Emunand to REDNand? (current Emunand for N3DS is a little around 1.8gb)

Hi d0k3 can your change your make file on emunand9 startergen that any one how is on linux can make this starter bin to.
For the bat file is only on line how need changed cp = linux, copy = windows

plz fix this

just warning you in advance what to expect

While using the select button in main menu for ejecting the sd card and inserting a new SanDisk 64GB card EmuNAND9 was freezing. Was occuring multiple times.

Since the card was delivered with pre formated exFAT I delete the partitions on the card with Windows disk part (clean option).

After that EmuNAND9 was working with the new 64GB card.

Using: EmuNAND9 20160420