Hacking Emunand vs Sysnand A9LH

[Bullseye]

Does anyone know the boot up time for a CFW-less/hax-less o3ds and n3ds?

 

[Supster131]

Does anyone know the boot up time for a CFW-less/hax-less o3ds and n3ds?

6-9 seconds I think.

 

[Bullseye]

Ok, thanks, so booting up with A9LH at around 9-11 seconds is great! It's more or less what I'm getting in my O3DS (slower) and N3DS with A9LH.

And I still have to decide whether to use emunand or sysnand with it.

6-9 seconds I think.

 

[night_hawk]

Mine is a N3DS and it boots in emunand in less than 8 seconds (something like 7.90 or so)

 

[leonmagnus99]

mine boots 6-10 seconds into emuNAND.
al9h is beast.

 

[CrispyYoshi]

I prefer EmuNAND using A9LH, because, as awesome as it would be to have SysNAND booting slightly even faster, I would rather not deal with manually working around FIRM0/FIRM1 every time I update, and just update through System Settings using EmuNAND. It's faster/more convenient for updating, still has a 100% boot rate, but at the cost of a 1-2 second difference on bootup.

 

[Supster131]

I prefer EmuNAND using A9LH, because, as awesome as it would be to have SysNAND booting slightly even faster, I would rather not deal with manually working around FIRM0/FIRM1 every time I update, and just update through System Settings using EmuNAND. It's faster/more convenient for updating, still has a 100% boot rate, but at the cost of a 1-2 second difference on bootup.

You don't have to do anything when updating sysNAND?
The CFW does it for you automatically.

 

[CrispyYoshi]

You don't have to do anything when updating sysNAND?
The CFW does it for you automatically.

Really? I thought it just prevents updates from touching FIRM0/FIRM1. Currently, the CFWs support 10.7, but what will happen in the future, when Nintendo makes a change to FIRM0/FIRM1?

 

[Supster131]

Really? I thought it just prevents updates from touching FIRM0/FIRM1. Currently, the CFWs support 10.7, but what will happen in the future, when Nintendo makes a change to FIRM0/FIRM1?

It will be blocked.
As people have stated, Nintendo can make changes to the system, but it won't be easy. It probably wouldn't be worth their time.
When a new NATIVE_FIRM is released, nothing will happen as FIRM0/FIRM1 is being blocked by the CFW anyways. Only thing is that the CFW wouldn't work until it's updated to support the new FIRM, same way like with emuNAND.

 

[CrispyYoshi]

It will be blocked.
As people have stated, Nintendo can make changes to the system, but it won't be easy. It probably wouldn't be worth their time.
When a new NATIVE_FIRM is released, nothing will happen as FIRM0/FIRM1 is being blocked by the CFW anyways. Only thing is that the CFW wouldn't work until it's updated to support the new FIRM, same way like with emuNAND.

Whoa! Thank you for the clarification. Maybe I'll start using SysNAND, then!