Hacking Can I just flash 2.1.0 via Hardmod?

[eaturbrainz]

Spoiler: Backstory (for those interested)

I had just successfully got A9LH on my own N3DSXL, then my brother asked if I could do it to his. He has a o3DSXL, but looking at the 3ds.guide, the process was still the same. I got to the Decrypt9 step with no problems. At the part where I downgrade to 2.1.0, the "Auto CTRNAND Transfer" step (I'm not that dumb, I did the NAND backup), I got an error immediately after it checked the 2.1.0 file. I don't remember exactly what it said, but it was something along the line of file not found on SD. Unsure if it started writing to NAND or not, I returned to the Decrypt9 main menu, unmounted the SD, reinserted it, and tried again. No errors this time. I thought all was going well until I restarted the DS, and all I got was black screens and a blue light. I saw the warning about not having the SD card in while booting 2.1.0, but the SD card was actually plugged into my PC, getting ready for the A9LH install.

If anyone has any clues as to what happened (what I did wrong), feel free to pitch suggestions.

TLDR: Followed guide, something went sideways during 2.1.0 downgrade, have NAND backup, 3DS bricked.

I am getting ready to hardmod my brother's bricked o3DSXL, but a little confused about flashing to it. I've seen plenty of tutorials on dumping the NAND, but very little on writing to it. I'm assuming it's straight forward, but it doesn't hurt to ask.

Actual Question(s): Can I just write the 2.1.0 ctrtransfer.bin to the NAND and continue with the guide? Can I skip any steps and go straight to A9LH (doubt it, because of the OTP thing can only be taken pre 3.0)?

 

[proflayton123]

Spoiler: Backstory (for those interested)

I had just successfully got A9LH on my own N3DSXL, then my brother asked if I could do it to his. He has a o3DSXL, but looking at the 3ds.guide, the process was still the same. I got to the Decrypt9 step with no problems. At the part where I downgrade to 2.1.0, the "Auto CTRNAND Transfer" step (I'm not that dumb, I did the NAND backup), I got an error immediately after it checked the 2.1.0 file. I don't remember exactly what it said, but it was something along the line of file not found on SD. Unsure if it started writing to NAND or not, I returned to the Decrypt9 main menu, unmounted the SD, reinserted it, and tried again. No errors this time. I thought all was going well until I restarted the DS, and all I got was black screens and a blue light. I saw the warning about not having the SD card in while booting 2.1.0, but the SD card was actually plugged into my PC, getting ready for the A9LH install.

If anyone has any clues as to what happened (what I did wrong), feel free to pitch suggestions.

TLDR: Followed guide, something went sideways during 2.1.0 downgrade, have NAND backup, 3DS bricked.

I am getting ready to hardmod my brother's bricked o3DSXL, but a little confused about flashing to it. I've seen plenty of tutorials on dumping the NAND, but very little on writing to it. I'm assuming it's straight forward, but it doesn't hurt to ask.

Actual Question(s): Can I just write the 2.1.0 ctrtransfer.bin to the NAND and continue with the guide? Can I skip any steps and go straight to A9LH (doubt it, because of the OTP thing can only be taken pre 3.0)?

@gamesquest1 @vb_encryption_vb

 

[ihaveahax]

no, ctrtransfer needs to be done through Decrypt9WIP. you can unbrick the system via hardmod and that's it

 

[eaturbrainz]

no, ctrtransfer needs to be done through Decrypt9WIP. you can unbrick the system via hardmod and that's it

I just thought maybe hardmod would shorten the process. No big deal.

Thanks, for the quick reply.

 

[Ronhero]

You should have a nand backup before brick. I don't think you can plaintext the CTR but i could be wrong

 

[gamesquest1]

if you do the hard mod you can just skip all the ctrtransfer and do the otp less install without any risks

 

[The Real Jdbye]

if you do the hard mod you can just skip all the ctrtransfer and do the otp less install without any risks

1. OTPLess is for n3DS only.
2. OTPLess brick is not a NAND brick AFAIK. Hardmod can't do anything to unbrick it.

 

[eaturbrainz]

1. OTPLess is for n3DS only.
2. OTPLess brick is not a NAND brick AFAIK. Hardmod can't do anything to unbrick it.

So for a bricked o3ds, the only option is to unbrick and try again? (not complaining, just curious)

 

[The Real Jdbye]

So for a bricked o3ds, the only option is to unbrick and try again? (not complaining, just curious)

Pretty much.

 

[Ronhero]

1. OTPLess is for n3DS only.
2. OTPLess brick is not a NAND brick AFAIK. Hardmod can't do anything to unbrick it.

Care to elaborate a little moreabout a non nand brick? I had this happen once about a year ago and even a hard mod couldn't fix it

 

[vb_encryption_vb]

Care to elaborate a little moreabout a non nand brick? I had this happen once about a year ago and even a hard mod couldn't fix it

Must have been a MCU brick? I've fixed plenty of otpless bricks via hardmod and nand back up with no issues.

 

[The Real Jdbye]

Care to elaborate a little moreabout a non nand brick? I had this happen once about a year ago and even a hard mod couldn't fix it

From what I've heard, it's a low level MCU brick, no one really knows any details as to why it happens though.

Must have been a MCU brick? I've fixed plenty of otpless bricks via hardmod and nand back up with no issues.

Seems I was wrong then.

 

[vb_encryption_vb]

From what I've heard, it's a low level MCU brick, no one really knows any details as to why it happens though.

Seems I was wrong then.

Correct, nobody know's the reason behind it, but as long as you have a nand backup they are fine though.

MCU bricks are impossible to recover from, maybe once sighax comes available MCU bricks can be fixed?

 

[gamesquest1]

oops my bad, yeah otpless is n3ds only, but as vb said otpless bricks are perfectly recoverable if you have a nand backup

AFAIK the only way the mcu brick occurs outside of purposefully messing with mcu is by putting a n3ds into sleep mode on 2.1

 

[Ronhero]

Mine was from a system transfer about a year ago trying to system transfer between 9.5 emunand o3ds and 9.5 system nand n3ds

 

[HyperT]

oops my bad, yeah otpless is n3ds only, but as vb said otpless bricks are perfectly recoverable if you have a nand backup

AFAIK the only way the mcu brick occurs outside of purposefully messing with mcu is by putting a n3ds into sleep mode on 2.1

Sleep mode doesn't affect hardmod on n3ds

 

[vb_encryption_vb]

Sleep mode doesn't affect hardmod on n3ds

It does on 2.1 you will brick and not recover.

 

[HyperT]

It does on 2.1 you will brick and not recover.

Oh, I think it might have been one of your posts from a while back that made me think it was recoverable...

 

[vb_encryption_vb]

Must be something else related to 2.1 brick, but sleep mode is permabrick as it's MCU.

 

[HyperT]

Must be something else related to 2.1 brick, but sleep mode is permabrick as it's MCU.

this thread I think: https://gbatemp.net/threads/n3ds-possibly-bricked-by-closing-lid-while-on-wifi-on-2-1.419184/
But I guess your post was made before it was known to be a mcu-brick