Hacking N3DS XL Bricked when updating

[ScarletDreamz]

So basically i'm screwed without a hardmod?

And a Nand BackUp.

 

[loneZ]

And a Nand BackUp.

I have a Nand Backup but I can't do anything with my 3ds right now :/

 

[ScarletDreamz]

I have a Nand Backup but I can't do anything with my 3ds right now :/

You can HardMod it, or use it as a nice Paper Holder.

 

[loneZ]

You can HardMod it, or use it as a nice Paper Holder.

Or Hardmod it into a cool Paper Holder

 

[Arkansaw]

Not much can be done when almost everyone just blindly follow a guide that recommends updating sysnand and ditching emunand

 

[darkziosj]

Well now im scared to update i really don't want to brick right now.

 

[acidmango]

I'm pretty sure my Luma was sittin' at 6.3.1 when I attempted to update from 11.1 to 11.2 and failed.
Hopefully hardmod and restored NAND will fix it, if not I'm content playing around with my o3dsXL until the switch launch [=

 

[Aurora Wright]

My N3DS running Luma with A9LH was bricked after I updated the system firmware. Luma is up to date as I checked before updating my 3ds. I can't go into other menus by holding down the buttons while booting.

What was the source 3DS version? Also did you use Star updater to update Luma? That mistakenly updated to nightlies for a while, and maybe that nightly had some issues with this?

 

[upfromtheskies]

This stuff doesn't happen with menuhax, just sayin. If you get this fixed somehow without a hardmod, I'd suggest switching to a safer set up until you absolutely need A9LH.

 

[YourHero]

I thought A9LH was supposed to make our 3DS unbrickable basically? Like the Wii Bootmii Boot2 did for the Wii. Now it's not even safe to update through Luma?

 

[HyperT]

@acidmango that's not the latest so tey witj the 6.6

No one has mentioned or for the a9lh version that was being used before updating

 

[satan89]

I know this happens to the tiniest fractions of people, but isn't I'm starting to feel menuhax + emuNAND is the safer option. Sure it's a slower boot and has a bad boot rate, but otherwise it's unbrickable.
Everytime I plan on A9LHing my 3ds consoles, a thread like this pops up and makes me hesitate.

Sorry OP, hope you manage to fix your 3ds

 

[ThisIsDaAccount]

For everyone who updated:

1) Did you brick?
2) What version of Luma were you on?
2) What type of 3ds do you have?
4) What version of luma (if any) is on your CTRNAND?

 

[Quantumcat]

I know this happens to the tiniest fractions of people, but isn't I'm starting to feel menuhax + emuNAND is the safer option. Sure it's a slower boot and has a bad boot rate, but otherwise it's unbrickable.
Everytime I plan on A9LHing my 3ds consoles, a thread like this pops up and makes me hesitate.

Sorry OP, hope you manage to fix your 3ds

Except when you update your sysNAND and render your device nearly unhackable.
Or you install a bad cia on sysNAND and break it, needing a hardmod.

Yeah menuhax is really safe :-p

 

[satan89]

Except when you update your sysNAND and render your device nearly unhackable.
Or you install a bad cia on sysNAND and break it, needing a hardmod.

Yeah menuhax is really safe :-p

Why would you update sysNAND? My 3ds directly boots to emuNAND. Everything I do is on emuNAND. I am aware that a9lh can do emuNAND as well, I think it's a safer option even on a9lh.

 

[Quantumcat]

Why would you update sysNAND? My 3ds directly boots to emuNAND. Everything I do is on emuNAND. I am aware that a9lh can do emuNAND as well, I think it's a safer option even on a9lh.

For example, you go into an option in Settings that reboots your console without you realising. Or you touch the key that makes you boot into sysNAND by accident when starting up. Or someone else gets hold of your system. Or you play a game that reboots you and you're using a CFW where this reboots you to sysNAND. Or your SD card or reader plays up a little and it boots without using the SD card files. Lots of ways.

 

[satan89]

For example, you go into an option in Settings that reboots your console without you realising. Or you touch the key that makes you boot into sysNAND by accident when starting up. Or someone else gets hold of your system. Or you play a game that reboots you and you're using a CFW where this reboots you to sysNAND. Or your SD card or reader plays up a little and it boots without using the SD card files. Lots of ways.

Yeah true, but that's not really an argument, we are talking actual human errors causing an update (not a brick technically). What if someone decides to delete your a9lh payload backup on your PC? And your SD card gets formatted or lost? These human errors can happen on a9lh as well. We are not discussing that, I'm talking about bricks that happen when you actually follow a guide, like the otpless a9lh and OPs issue like updating when many others haven't had the same problem happening. I'm not complaining about a9lh, I know it's the better hack, but it looks like of late there are some minor issues affecting a handful of people and till those issues are resolved it's probably best not to advertise it as the safest hax.

Also, what I do is keep a different theme for sysNAND(red) and emuNAND(blue or white) so I can tell the difference. Also you forgot to mention how eShop in emuNAND can update sysNAND for menuhax, yeah it's a problem with that.

 

[MadMageKefka]

I have a Nand Backup but I can't do anything with my 3ds right now :/

When you boot without the SD card in, does the blue light turn itself off after a second, or does it stay on?

 

[ThisIsDaAccount]

For everyone who updated:

1) Did you brick?
2) What version of Luma were you on?
2) What type of 3ds do you have?
4) What version of luma (if any) is on your CTRNAND?

Can anyone confirm this information to see if maybe bricks have one of these in common? Thanks again!

 

[Quantumcat]

What if someone decides to delete your a9lh payload backup on your PC?

You redownload it from Luma's GitHub

And your SD card gets formatted or lost

As above, plus buy a new SD if possible

Neither of these things are going to brick you, update you, render your console unhackable, or even lose you your data.