Hacking 3DS not turning on after system and Luma update

[Haryor]

I've had CFW with B9S in it's latest version, with everything working all right. So, I got the latest system update, and couldn't boot (getting the ARM exception handler). After updating my Luma .firm and .3dsx with the 10.2.1 ones, my New 3DS just went to that state of the blue light turning on and then off almost instantly.

I followed the instructions here:

• CFW: I formatted my 2ds's sd card and now it wont turn on [post #17]

Which means I formatted my card with MiniTool, tested with h2test2w, etc. In the end, I used arm9loaderhax.bin from Luma3DS v7.0.5 and SafeB9SInstaller.firm renamed as boot.firm from SafeB9SInstaller v0.0.7, which led me to SafeB9SInstaller v0.0.7 install screen. @TurdPooCharger then gives the instruction to follow the Updating B9S guide but, when I added the boot9strap folder to my SD card with the firm and firm.sha files, my 3DS when to its previous state of the light turning on and then off. Then, removing the folder again led me back to the B9SInstaller screen.

I would immensely appreciate any help.

 

[Ricken]

So, I got the latest update, and received the ARM exception handler. After updating my Luma files, my New 3DS just went to that state of the blue light turning on and then off almost instantly.

I followed the instructions here:

• CFW: I formatted my 2ds's sd card and now it wont turn on [post #17]

Which means I formatted my card with MiniTool, tested with h2test2w, etc. In the end, I used arm9loaderhax.bin from Luma3DS v7.0.5 and SafeB9SInstaller.firm renamed as boot.firm from SafeB9SInstaller v0.0.7, which led me to SafeB9SInstaller v0.0.7 install screen. @TurdPooCharger then gives the instruction to follow the Updating B9S guide but, when I added the boot9strap folder to my SD card with the firm and firm.sha files, my 3DS when to its previous state of the light turning on and then off. Then, removing the folder again led me to the B9SInstaller screen.

I would immensely appreciate any help.

Have you tried putting this boot.firm on the root of your SD card?
If I'm reading what you said right, you had an A9LH installation, installed B9S, but never put the Luma payload as boot.firm after installing B9S

 

[Haryor]

Have you tried putting this boot.firm on the root of your SD card?
If I'm reading what you said right, you had an A9LH installation, installed B9S, but never put the Luma payload as boot.firm after installing B9S

Oh I wasn't very clear, sorry. I've had CFW working all right for a long time, with B9S installed in its latest version. Due to the update, I had to update Luma because I was getting the ARM exception handler. However, after updating, I started not being able to boot my 3DS, with or without an SD card.

 

[lone_wolf323]

Oh I wasn't very clear, sorry. I've had CFW working all right for a long time, with B9S installed in its latest version. Due to the update, I had to update Luma because I was getting the ARM exception handler. However, after updating, I started not being able to boot my 3DS, with or without an SD card.

and it was the luma 10.2.1 boot.firm that you got afterwards?

 

[Haryor]

and it was the luma 10.2.1 boot.firm that you got afterwards?

Yes!

 

[Ricken]

but, when I added the boot9strap folder to my SD card with the firm and firm.sha files, my 3DS when to its previous state of the light turning on and then off

ah wait, I'm smart. It's not letting you update B9S?

 

[Haryor]

ah wait, I'm smart. It's not letting you update B9S?

Since my 3DS won't even turn on, I can't actually do anything.

Only thing that gave me some results was, as per @TurdPooCharger instructions, leave only the arm9loaderhax.bin from Luma3DS v7.0.5 and SafeB9SInstaller.firm renamed as boot.firm from SafeB9SInstaller v0.0.7 in the root of my SD card, with nothing else. I still have the rest of my files backed up, of course, should I need them.

This takes me to the SafeB9SInstaller screen, but I can't do anything with it (probably because there's nothing else in the files). The poster instructs that, should one get to this installer screen, one should follow the instructions in Updating B9S. When I do that (which includes adding a boot9strap folder to the card), my 3DS goes back to its state of turning off instantly.

 

[fmkid]

I used arm9loaderhax.bin from Luma3DS v7.0.5 and SafeB9SInstaller.firm renamed as boot.firm from SafeB9SInstaller v0.0.7, which led me to SafeB9SInstaller v0.0.7 install screen. @TurdPooCharger then gives the instruction to follow the Updating B9S guide but, when I added the boot9strap folder to my SD card with the firm and firm.sha files, my 3DS when to its previous state of the light turning on and then off. Then, removing the folder again led me to the B9SInstaller screen.

Weird... It has no sense/explanation (at least to me)

• If SafeB9SInstaller renamed as boot.firm loads directly, then your console already has B9S (but perharps it could be the 1.0 or the 1.2/1.3 versions). Could you try to put Luma 7.1 version boot.firm on the root your SD card and see what happen?
• And that behaviour associated to put or remove the "boot9strap" folder is totally weird/absurd at all

 

[Ricken]

Weird... It has no sense/explanation (at least to me)

• If SafeB9SInstaller renamed as boot.firm loads directly, then your console already has B9S (but perharps it could be the 1.0 or the 1.2/1.3 versions). Could you try to put Luma 7.1 version boot.firm on the root your SD card and see what happen?
• And that behaviour associated to put or remove the "boot9strap" folder is totally weird/absurd at all

Yeah I just read it over like five times and the only idea I even nearly concocted was a system update introduced a bug in SafeB9SInstaller where you can't install it on the latest firmware or something dumb and unlikely like that

only the arm9loaderhax.bin

I'm almost certain you can just delete this now, if you're booting the .firm then your arm9loaderhax is gone

 

[fmkid]

Yeah I just read it over like five times and the only idea I even nearly concocted was a system update introduced a bug in SafeB9SInstaller where you can't install it on the latest firmware or something dumb and unlikely like that

Yeah. Perharps is a behaviour associated to SafeB9SInstaller used directly as boot.firm. There's not another explanation for that

The guide to update B9S indicates to use SafeB9SInstaller as an usual Luma payload (onto "luma/payloads" path). Then, is (apparently) always necessary to have Luma as boot.firm

 

[Haryor]

Attached photo is the screen I get with the installer.

This is what the poster I mentioned recommends:

"Temporarily rename SafeB9SInstaller as the boot.firm, do Updating B9S, and then Finalizing Setup."

 

[lone_wolf323]

Attached photo is the screen I get with the installer.

This is what the poster I mentioned recommends:

"Temporarily rename SafeB9SInstaller as the boot.firm, do Updating B9S, and then Finalizing Setup."

That shows you got a form of b9s running with a9lh not found. What does your sd card set up look like right now? Cause it seems theres things missing

 

[fmkid]

Attached photo is the screen I get with the installer.

This is what the poster I mentioned recommends:

"Temporarily rename SafeB9SInstaller as the boot.firm, do Updating B9S, and then Finalizing Setup."

Did you do that I said before?

Could you try to put Luma 7.1 version boot.firm on the root your SD card and see what happen?

To follow the "Updating B9S" guide is mandatory that your console has a Luma version running on. Just renaming SafeB9SInstaller as boot.firm doesn't work (apparently)

 

[Haryor]

Well I just got it to work. I'm so, so relieved. So, although I did all the formatting and testing with that other SD card, I just tried now with another, newer and much bigger. Not only that, I also put secret-sector.bin along with the .firm and .firm.sha files in the boot9strap folder. So, it could have been any of these two things (though the installer says the secret sector wasn't necessary, it did have that message about the sig patches)

Thanks a lot for everyone who replied!