Hacking Something wonky happened when I tried to install arm9loaderhax

[Supah]

I was following a guide I found out a little too late was fairly dated (a couple months old)

I was following this video


When I got to this point, I installed arm9loaderhax.3dsx as instructed but panicked when it immediately rebooted into reinand, even though this wasn't supposed to happen. Turning my system on and off again it continued to reboot reinand in this fashion so I assume the arm9 was at least partially successful, but I was worried something was wrong for it to behave this way so I switched to Plailect's guide, however I found out that loading the safearm9 installer gives only a black screen. I tried to flash my emunand and sysnand backups however otphelper and emunand9 both flash a red screen on the bottom screen and then kick me back out to the cold boot menu.

Also between adding in the files specified in the Plailect guide my system now cold boots like it used to with the usual glitchiness.

Does anyone have any idea what went wrong or know how I can flash my backups?

 

[GothicIII]

Don't follow videos they are mostly outdated. Use like you already wrote Plailect's guide instead. If you would have followed it from beginning this thread would'nt be here.

Start from new if you haven't got your OTP yet. If you have, follow the last part (5) of the tutorial. Don't mess with things you don't understand.

 

[TuxSH]

@OP at least you have backups

What's your console model, and the version of your sysnand? If it's 9.3 or higher, no wonder D9 and others will work... in that case you just have to do everything from scratch again (using Plailect's guide) . You did what you had to do, flashing your nand backups.

it immediately rebooted into reinand

With al9h installed, arm9loaderhax.bin is the file that will be booted.

 

[XRaTiX]

With al9h installed, arm9loaderhax.bin is the file that will be booted.

That's not weird? Reinand supposedly is the arm9loaderhax.bin,that can't be.

 

[TuxSH]

I'm in fact saying this is the intended behavior

 

[XRaTiX]

I'm in fact saying this is the intended behavior

That's the normal behavior indeed.

I just saying this,because only Cakes and Luma3DS can be booted from arm9loaderhax.bin if I not wrong xD.

 

[Froster]

That's the normal behavior indeed.

I just saying this,because only Cakes and Luma3DS can be booted from arm9loaderhax.bin if I not wrong xD.

ReiNAND can be booted with A9LH as well...

 

[XRaTiX]

ReiNAND can be booted with A9LH as well...

Oh,I didn't know that,sorry.

 

[sora10pls]

How did you compile your arm9loaderhax.3dsx? I feel as if your A9LH file didn't include screen-init due to it being outdated.

I once had a similar problem to where I could only boot into Luma3DS on my o3DS, but no other payloads (i.e. CtrBootManager9, Decrypt9, etc.). What I did to fix this was simply recompile my arm9loaderhax.3dsx with https://felipejfc.com/a9lh and installed it again. This website includes screen-init so it may be worth your time to try this out.

 

[Supah]

Well here's the deal, I still had homebrew access so I started with the 2nd part of Plai's guide, I tried a few times to downgrade to 9.2.0U on account of the fact that my sysnand was showing Rei 10.7, after about 4 or 5 attempts where it would hang at HAX INIT without doing anything else I decided to check my firmware and now it is reading 9.2.0U. And browserhax works on it too. Safe AL9H installer is still hanging on a black screen any time i try to run it, emunand is still nonfunctional, and I don't trust the original way I installed arm9 with the older less safe installer in the current state the system is in

EDIT: If its some kind of partial downgrade, I still can't actually get PlaiSysUpdater to do a full one

I originally got a downgrade to work in one try with safesysupdater, but I'm not sure if this is less safe or outdated and similarly don't want to risk anything I don't have to

 

[Supah]

Sorry for the double post, I restored my files from my SD backup i made before I tried "fixing" my installation of AHL9 and its booting instantly as originally intended, and is reading Rei 10.7 in the system settings on boot... am I ok to leave it like this?

EDIT: I'm missing features I would have gotten from Plai's guide and also still can't access those homebrew apps for reasons obvious, so I'm going to try to downgrade again with this sdcard setup

EDITx2: Same problem, hangs at HAX INIT

 

[samiam144]

What features? As far as I can tell, a9lh is working for you just fine.

Edit: ^Assuming you fixed those issues you mentioned two posts above.
Don't worry about the "less safe" way you did it; many members here set up a9lh with the same older methods (no OTPHelper, no SafeA9LHInstaller, etc.). If it is booting straight to reinand, then it is working for you.
What you can do (if you really want to) is to restore an older sysnand backup using Decrypt9 ("Keep A9LH" option). But I'd wait for someone else's expertise before doing that.

 

[Supah]

"You will no longer be able to boot without the SD card in, that is normal.
You will now boot a Custom Firmware based SysNAND by default.
You can now hold Select on boot to launch the Luma3DS configuration menu.
You can now hold Start on boot to launch Decrypt9, a full featured NAND tool.
You can now hold Y on boot to launch EmuNAND9, a full featured RedNAND and SD management tool.
You can now hold X on boot to launch Uncart, a tool for converting a physical game cart to an installable file.
"

3-6, straight from the guide

Not to mention being unable to access emunand9 or something else to restore a nand backup is unnerving

 

[samiam144]

"You will no longer be able to boot without the SD card in, that is normal.
You will now boot a Custom Firmware based SysNAND by default.
You can now hold Select on boot to launch the Luma3DS configuration menu.
You can now hold Start on boot to launch Decrypt9, a full featured NAND tool.
You can now hold Y on boot to launch EmuNAND9, a full featured RedNAND and SD management tool.
You can now hold X on boot to launch Uncart, a tool for converting a physical game cart to an installable file.
"

3-6, straight from the guide

Not to mention being unable to access emunand9 or something else to restore a nand backup is unnerving

I made an edit to my post just now.
The last 4 features you mentioned are for Luma3DS, I'm not sure if ReiNAND provides those features. The first feature, I think Reinand can do that too (again, not sure). If you want those features, then switch to Luma3DS. A9LH is working fine for you, you're just not using the CFW that the Plailect guide uses.
Basically, go to Part 5 of the Plailect Guide and you will have those features.

 

[Temptress Cerise]

"You will no longer be able to boot without the SD card in, that is normal.
You will now boot a Custom Firmware based SysNAND by default.
You can now hold Select on boot to launch the Luma3DS configuration menu.
You can now hold Start on boot to launch Decrypt9, a full featured NAND tool.
You can now hold Y on boot to launch EmuNAND9, a full featured RedNAND and SD management tool.
You can now hold X on boot to launch Uncart, a tool for converting a physical game cart to an installable file.
"

3-6, straight from the guide

Not to mention being unable to access emunand9 or something else to restore a nand backup is unnerving

Never tried ReiNAND CFW, so not sure how it works. But the A9LH guide uses Luma3DS. Try doing the preparatory work section only of part 5. That should get you setup with Luma3DS and those other tools.
https://github.com/Plailect/Guide/wiki/Part-5-(arm9loaderhax)

 

[Supah]

If I follow the prep work there then the system starts booting as if it wasn't a9lh anymore, further while the luma cfg menu works it won't even let me load luma from the menu, it just goes to a red screen and locks

EDIT: I've managed to get Decrypt9/Emunand9 fired up finally via the start/y on bootup, but everything else is still a mess, its not booting like its on a9lh, its booting like it was before and the luma3ds on that menu still only hangs

EDITx2: I'm going to continue following the guide since the A9LH and the firmware are ok, and see what I can do about luma afterwards I guess. I'm not sure where I've gone wrong there

EDITx3: FINALLY. It seems like everything is working now as intended, thanks for the help guys