Hacking Why can't we use an EmuNAND with the 2.1.0 ctrasnsfer to install A9LH?

[porkiewpyne]

well if he doesn't want to risk a mcu brick he could just do the otpless a9lh install, then as long as he makes a nand backup he can always recover if he bricks, but as mentioned when otpless was under debate for removal, the brick chance is super super tiny (like 1/6000)

But then again, that miniscule risk is still there and there hasn't been any way around it outside not being that unlucky. Keep in mind that we are talking about a person who isn't keen on the safer alternative (0% brick afaik excluding user errors) whereby the only rule is to not close the lid during that specific short span of time.

 

[leon315]

i use luma3ds with emunand,and all games work fine

 

[The Catboy]

An interesting note since the OP is a very recent member. We actually used to have to setup an emuNAND on 2.1, then flash that directly to the system to install A9LH. It was actually a lot more risky and required shit tons of steps.

 

[mirsao]

Being able to do this would make the process much safer, as bricking an EmuNAND by closing the lid on a New 3DS is more of a minor setback than an unrecoverable brick

if you shut the lid on an n3ds running 2.1 it bricks the mcu. using an emunand will not change anything

 

[nechigawara]

i use luma3ds with emunand,and all games work fine

Did you mean, you're using menuhax + Luma3DS?

 

[gamesquest1]

But then again, that miniscule risk is still there and there hasn't been any way around it outside not being that unlucky. Keep in mind that we are talking about a person who isn't keen on the safer alternative (0% brick afaik excluding user errors) whereby the only rule is to not close the lid during that specific short span of time.

yeah I know why the guide opts for the downgrade method, but seeing as the op seems to be paranoid or ocd about closing his consoles lid every 7 seconds so unable to avoid closing the lid on 2.1 it's better in his bizarre paranoid scenario to opt for a method with a recoverable brick method than a method with a unrecoverable brick risk........for everyone else they should just follow the guide to the letter

 

[nechigawara]

yeah I know why the guide opts for the downgrade method, but seeing as the op seems to be paranoid or ocd about closing his consoles lid every 7 seconds so unable to avoid closing the lid on 2.1 it's better in his bizarre paranoid scenario to opt for a method with a recoverable brick method than a method with a unrecoverable brick risk........for everyone else they should just follow the guide to the letter

Or another route, don't play 3DS. Since 3DS also can brick by official update (happen once already )

 

[The Catboy]

I seriously don't understand why the lid closing flaw is always brought up. Is it really that tempting to close your lid during this install? Does everyone really get to 2.1 and say, "Well, I got this far, time for a smoke break!" then close their systems?
I've even had paranoid Menuhax fans bring it up as a "counter-argument" against installing A9LH. (Seriously, that happened)
I don't understand why this is always brought up like it's a common thing? It happened a few times before it was added to the guide and basically hasn't happened since it was added to the guide.

 

[nechigawara]

I seriously don't understand why the lid closing flaw is always brought up. Is it really that tempting to close your lid during this install? Does everyone really get to 2.1 and say, "Well, I got this far, time for a smoke break!" then close their systems?
I've even had paranoid Menuhax fans bring it up as a "counter-argument" against installing A9LH. (Seriously, that happened)
I don't understand why this is always brought up like it's a common thing? It happened a few times before it was added to the guide and basically hasn't happened since it was added to the guide.

People have different way of thinking. Just let them paranoid as much as they can.
If they can't even keep the lid open for 15 - 30 mins, they should think about how they gonna live.
I hacked 2 N3DS without lid problem at all. This is totally user f*cking error.
If nobody can't find arm9 exploit on 11.3 and those menuhax people screw, they can't blame anyone but themselves.

 

[The Catboy]

People have different way of thinking. Just let them paranoid as much as they can.
If they can't even keep the lid open for 15 - 30 mins, they should think about how they gonna live.
I hacked 2 N3DS without lid problem at all. This is totally user f*cking error.
If nobody can't find arm9 exploit on 11.3 and those menuhax people screw, they can't blame anyone but themselves.

This is just one of those things I keep seeing though and it just blows my mind that it's brought up all the time. People act like it's as common as Gateway threads after the 11.3 update.
I have hacked 7 different systems using 5 different methods. I haven't run into a brick, yet. I just hacked my 3rd New3DS over the weekend.

 

[nechigawara]

This is just one of those things I keep seeing though and it just blows my mind that it's brought up all the time. People act like it's as common as Gateway threads after the 11.3 update.
I have hacked 7 different systems using 5 different methods. I haven't run into a brick, yet. I just hacked my 3rd New3DS over the weekend.

Just let them be, don't bother them. Help only people who glad reciveing your help.

 

[BL4Z3D247]

While we're dishing out warnings, don't system format on 2.1 with a N3DS/2DS or you'll brick. This is mentioned in the guide regarding 2DSes but not N3DSes.

 

[Halvorsen]

Also the fact that closing the lid on N3DS 2.1 running in EmuNAND would still brick the system. It's an MCU brick, not a NAND brick.

This has not been confirmed

 

[OldSchoolTech]

Anyone wanna downgrade their N3DS to 2.1 install an emunand and try it xD

 

[Halvorsen]

Anyone wanna downgrade their N3DS to 2.1 install an emunand and try it xD

I do have a working motherboard if anyone wants to send me a bricked n3DS XL to test

 

[OldSchoolTech]

I do have a working motherboard if anyone wants to send me a bricked n3DS XL to test

All I have is a spare O3DS board on 11.3 it's not much use as of yet. I really don't wanna brick my brand new ds though lol.

 

[Halvorsen]

All I have is a spare O3DS board on 11.3 it's not much use as of yet. I really don't wanna brick my brand new ds though lol.

It wouldn't matter as it's an old 3DS anyway, it wouldn't brick lol.

 

[Majickhat55]

This has not been confirmed

I don't think it needs to be since it's confirmed said actions causes an MCU brick, not a NAND brick. The system only has one MCU regardless of the NAND in use, so it's going to brick either way.

 

[Halvorsen]

I don't think it needs to be since it's confirmed said actions causes an MCU brick, not a NAND brick. The system only has one MCU regardless of the NAND in use, so it's going to brick either way.

Again, this has not been confirmed. Everything points to a NAND brick anyway. An MCU brick would cause the lights and power button not to function at all in the first place.

 

[Xiphiidae]

Again, this has not been confirmed. Everything points to a NAND brick anyway. An MCU brick would cause the lights and power button not to function at all in the first place.

I'm actually inclined to agree. The only 'confirmed' N3DS-2.1-lid bricks I've seen have resulted in "An error has occurred, please turn off the power" messages, which perhaps fits more closely with the original theory that they're due to invalid Spotpass/Update data impacting the NAND in some way. I'd love to see some evidence to support the claim that it is an MCU brick.