Hacking How to unbrick using A9LH?

[Lycan911]

(Just to make it clear, I didn't brick my console, I'm just curious.)

Now that that's out of the way, here's the question: How exactly does one unbrick a 3DS using A9LH without a hardmod? I've seen that in the "pros" section of pretty much any MenuHax vs. A9LH fight, but that's pretty much all everyone says: "Hurr durr you can unbrick without a hardmod.".
But NO ONE says how exactly is that unbrick possible, how to do it, what are the steps... Nothing!

So could someone please explain this to the peepz who might be interested in this?

Thanks.

 

[xtheman]

I to would like to know. I'm going through a brick risk and i want to know how to unbrick once i set it up

 

[Lumince]

It can load a payload before the system boots up. So as long as you have a backup of your sysnand or emunand you can flash it and have it fixed again. Decrypt9 is what is used

 

[linuxares]

I would think it's for example with AuReiNand if you followed the OTP Guide.

If you hold L+R it will autoboot Decrypt9. From there you can restore a Xnand (emu/sys) without need the help from an exploit on the system itself. Since all is on a sdcard. Sure if the firm0 and firm1 gets FUBAR, they our out of luck. But then your system would be a brick anyway from a hardware failure rather than a software issue.

 

[Conn0r]

Just an important message I'd like to share. If you are installing A9LH or updating it, you are not protected from a brick. You are only protected from bricks relating to (un)installing cias to the nand.

Source: me ;(

 

[Lumince]

Just an important message I'd like to share. If you are installing A9LH or updating it, you are not protected from a brick. You are only protected from bricks relating to (un)installing cias to the nand.

Source: me ;(

Well yes, flashing a dump to say, a fried nand chip would do nothing. Hardware failure cant be fixed by dumps... idk why you would think that?

 

[Conn0r]

Well yes, flashing a dump to say, a fried nand chip would do nothing. Hardware failure cant be fixed by dumps... idk why you would think that?

I didn't say anything about a hardware failure. I was just saying if something goes wrong in the install process then it would be a permabrick (of course you could always hard mod)

 

[Lumince]

I didn't say anything about a hardware failure. I was just saying if something goes wrong in the install process then it would be a permabrick (of course you could always hard mod)

Ahh, sorry about that then. I am really tired atm. xD And yea, I think most guides warn of risks.

 

[Conn0r]

Ahh, sorry about that then. I am really tired atm. xD And yea, I think most guides warn of risks.

Lol it's ok man.

 

[crimpshrine]

I didn't say anything about a hardware failure. I was just saying if something goes wrong in the install process then it would be a permabrick (of course you could always hard mod)

I have always wondered can you always recover with a hard mod? (Short of hardware failure of the flash on the unit)

Are there any circumstances other than hardware failure that you could put your NAND into a state that even a hardmod cannot fix?

Thanks

 

[Conn0r]

I have always wondered can you always recover with a hard mod? (Short of hardware failure of the flash on the unit)

Are there any circumstances other than hardware failure that you could put your NAND into a state that even a hardmod cannot fix?

Thanks

Misuse of hammer and motherboard.

Maybe bricking and not having a backup.

Nandmods fix because it overwrites "the everything" including the possible mismatched firm partitions and whatever system cias you may or may not have deleted.
Edit: AKA: Hardmods fix yo shit.

 

[Lycan911]

So wait, even if the A9LH SysNAND bricks, it's still possible to access Decrypt9 using R+L (or whatever your shortcut is) on boot? I thought that would brick too?

 

[RealityNinja]

So wait, even if the A9LH SysNAND bricks, it's still possible to access Decrypt9 using R+L (or whatever your shortcut is) on boot? I thought that would brick too?

If you corrupts firm0 or firm 1 partition, your 3ds is bricked! (also a9lh). With an hardmod, you can access the NAND in order to repair the sysnand, so the 3ds.

 

[Lycan911]

If you corrupts firm0 or firm 1 partition, your 3ds is bricked! (also a9lh). With an hardmod, you can access the NAND in order to repair the sysnand, so the 3ds.

And how would one avoid Firm1 and Firm0 corruption?
What are some things to avoid doing?

 

[oFire]

And how would one avoid Firm1 and Firm0 corruption?
What are some things to avoid doing?

Once you get a9lh installed, dont try to update it or touch it. Unless something super new comes out that makes it crucial to update it, the risk for many people just outweighs the benefits.

 

[Just Passing By]

Edit: nvm

 

[Raylight]

Once you get a9lh installed, dont try to update it or touch it. Unless something super new comes out that makes it crucial to update it, the risk for many people just outweighs the benefits.

wait till safea9lh installer gets finished then we can update safer then what we currently can. what more can be done anyways.

 

[Ryccardo]

Are there any circumstances other than hardware failure that you could put your NAND into a state that even a hardmod cannot fix?

All MMC-compatible chips can be programmed in software to turn read-only...

 

[Lycan911]

Once you get a9lh installed, dont try to update it or touch it. Unless something super new comes out that makes it crucial to update it, the risk for many people just outweighs the benefits.

What do you mean by "update"? Updating the SysNAND's firmware, updating AuReiNand, or updating A9LH itself?

I already have A9LH with updated SysNAND and AuReiNand, so knowing which of the three is the most dangerous to mess with would be helpful.

 

[Just Passing By]

What do you mean by "update"? Updating the SysNAND's firmware, updating AuReiNand, or updating A9LH itself?

I already have A9LH with updated SysNAND and AuReiNand, so knowing which of the three is the most dangerous to mess with would be helpful.

Updating a9lh.