Hacking System Update before arm9, causes error message?!

[Era]

I was hacking my bf new 3ds xl, and I was following the guide to a "T". Since I couldn't use browserhaxs to access homebrew I've been using my oot catridge. After downgrading to ver 2.1, I need to update to be able to access oot (which updated the system to 4.3.0.). Well I couldn't access homebrew on my catridge with the version being so low, so I tried to update the system again and it just keeps giving me an error message when I power it on.

 

[Boured]

I was hacking my bf new 3ds xl, and I was following the guide to a "T". Since I couldn't use browserhaxs to access homebrew I've been using my oot catridge. After downgrading to ver 2.1, I need to update to be able to access oot (which updated the system to 4.3.0.). Well I couldn't access homebrew on my catridge with the version being so low, so I tried to update the system again and it just keeps giving me an error message when I power it on.

So let me get this straight, you updated from 2.1 from System Settings on a N3DS?

 

[FTRBND]

I was hacking my bf new 3ds xl, and I was following the guide to a "T". Since I couldn't use browserhaxs to access homebrew I've been using my oot catridge. After downgrading to ver 2.1, I need to update to be able to access oot (which updated the system to 4.3.0.). Well I couldn't access homebrew on my catridge with the version being so low, so I tried to update the system again and it just keeps giving me an error message when I power it on.

What kind of error message?

 

[Era]

Error Message: Error Has Occurred. Hold down the Power Button to turn the power off.

 

[Boured]

Error Message: Error Has Occurred. Hold down the Power Button to turn the power off.

If you went to 2.1 on a N3DS it isn't necessary. N3DS's are able to install A9LH without a OTP. Given from the info I have gotten I can guess you updated the system from 2.1 on a N3DS.


You may have screwed yourself over by doing so. As the 2.1 firmware installed the newest firmware for the O3DS, which is incompatible with a N3DS save for the 2.1 downgrade.

I also question whether you followed the guide to the "T" as if you did you would have saw that you just need to downgrade to 9.2 and install A9LH from a modified version of SafeA9LHInstaller, which eliminates the 2.1 downgrade completely on a N3DS.

 

[Jayster_2]

lol exposed.

 

[Quantumcat]

What guide were you using?? Obviously not https://plailect.github.io/Guide

 

[N7Kopper]

If you went to 2.1 on a N3DS it isn't necessary. N3DS's are able to install A9LH without a OTP. Given from the info I have gotten I can guess you updated the system from 2.1 on a N3DS.


You may have screwed yourself over by doing so. As the 2.1 firmware installed the newest firmware for the O3DS, which is incompatible with a N3DS save for the 2.1 downgrade.

I also question whether you followed the guide to the "T" as if you did you would have saw that you just need to downgrade to 9.2 and install A9LH from a modified version of SafeA9LHInstaller, which eliminates the 2.1 downgrade completely on a N3DS.

I wouldn't recommend doing so, unless safea9lhinstaller has been updated since my last checking. The version I last checked suffers from a race condition bug on an OTPless install where the OTP hash can be corrupted, causing a brick. It's rare, but when it happens, it's not user error, but the program's fault.

But, really. Updating from the option on 2.1? Before you even installed a9lh? I guess OP's avatar choice of Rosie the Riveter is fitting, considering that she was an incompetent riveter who quit so she wouldn't break a nail, before just marrying a rich dentist.

 

[Era]

I wouldn't recommend doing so, unless safea9lhinstaller has been updated since my last checking. The version I last checked suffers from a race condition bug on an OTPless install where the OTP hash can be corrupted, causing a brick. It's rare, but when it happens, it's not user error, but the program's fault.

But, really. Updating from the option on 2.1? Before you even installed a9lh? I guess OP's avatar choice of Rosie the Riveter is fitting, considering that she was an incompetent riveter who quit so she wouldn't break a nail, before just marrying a rich dentist.

Excuse me but all I did was ask for help and I get rude remarks about my avatar choice? I got someone to help me btw

 

[Boured]

Excuse me but all I did was ask for help and I get rude remarks about my avatar choice? I got someone to help me btw

Yeah they were pretty rude, though I hope you get it fixed.

 

[TylenKiD]

Did you ever get this fixed , I have the exact same problem

 

[kaos3force]

The same thing happened to me. I called nintendo and it was covered by the warranty.

 

[Jayster_2]

I called nintendo

Uh..

 

[MarioMasta64]

If you went to 2.1 on a N3DS it isn't necessary. N3DS's are able to install A9LH without a OTP. Given from the info I have gotten I can guess you updated the system from 2.1 on a N3DS.


You may have screwed yourself over by doing so. As the 2.1 firmware installed the newest firmware for the O3DS, which is incompatible with a N3DS save for the 2.1 downgrade.

I also question whether you followed the guide to the "T" as if you did you would have saw that you just need to downgrade to 9.2 and install A9LH from a modified version of SafeA9LHInstaller, which eliminates the 2.1 downgrade completely on a N3DS.

id say try a 9.2 ctrtransfer thats probably youre only hope

 

[conjoir]

I also question whether you followed the guide to the "T" as if you did you would have saw that you just need to downgrade to 9.2 and install A9LH from a modified version of SafeA9LHInstaller, which eliminates the 2.1 downgrade completely on a N3DS.

Kinda curious on where exactly in the guide it says this?

 

[MarioMasta64]

Kinda curious on where exactly in the guide it says this?

they removed it recently dont worry about it.