Hacking So...is my N3DS dead?

[daxtsu]

I'm not sure you can run a .3dsx file from A9LH. It would be great if you could, but I think payloads can only be binaries. If there was a binary version of HBL that would be great, but I think HBL needs to use the full 3DS hardware to run, not just ARM9 portion of it?? That's just an "ignorant" guess though, as all binaries I've seen run in a text mode with limited GUI, HBL has a decent GUI - taking advantage of other 3DS hardware.

The HBL requires the 3DS OS to be running, yes. That's why there's not already a way to run it directly from A9LH. When A9LH runs, you're running code on the bare metal with no fancy services to help you out. If FIRM (or I guess more correctly the NS module) can be patched to load something other than the home menu on boot, then one could probably boot directly into the HBL. That's just a theory though.

 

[3dsn00b]

The HBL requires the 3DS OS to be running, yes. That's why there's not already a way to run it directly from A9LH. When A9LH runs, you're running code on the bare metal with no fancy services to help you out. If FIRM (or I guess more correctly the NS module) can be patched to load something other than the home menu on boot, then one could probably boot directly into the HBL. That's just a theory though.

That's what I thought, because HBL needs to be further along the boot process than A9LH, A9LH is like milliseconds in.

Also, here is another interesting thing. I installed OTPHelper as a payload in the Luma3DS and tried to do the otp.bin -> opt0x108.bin feature. It said:

Could not open otp.bin!
opt.bin -> otp0x108.bin: failed!​

 

[pokebud]

Just a thought

I know you can dump and inject FIRM0/FIRM1 with Decrypt9, now I don't know if it can take donor FIRM0/FIRM1 but assuming you can I would assume that would fix your issue.

Maybe you should dump your FIRM0/FIRM1 so others can compare them to working versions unless they're console unique, then don't do that.

 

[linuxares]

Dumb question, can you clone your Sysnand to a Rednand/Emunand and see if the chip itself is borked? If you manage to boot Rednand/emunand you might be able to repair it from there.

 

[3dsn00b]

Dumb question, can you clone your Sysnand to a Rednand/Emunand and see if the chip itself is borked? If you manage to boot Rednand/emunand you might be able to repair it from there.

Yes already tried running from emuNAND as the default boot in Luma3DS by unchecking the Autoboot SysNAND feature. Even tried the default "L" trigger with it set as default. Doesn't work. I don' t think it's a NAND issue, I think it's deeper than that, either hardware or the FIRM0 is corrupted it's lower level than software or NAND.

 

[Asia81]

A fake cia with nand installation ?

 

[linuxares]

Have you tried to reinstall with SafeA9HLInstaller? I think it might detect corrupt FIRM.

http://gbatemp.net/threads/safea9lhinstaller.419577/ - here is how to do it

EDIT: Maybe this is the issue "- If updating from A9LH, it verifies that the NAND keystore is the correct one (just in case) and that FIRM0 is correct before using it."

 

[kingaz]

Try this:

1) Disable "Enable splash screen with no screen-init"

2) When your 3DS starts up, wait for a couple of minutes before turning it off.

3) If it continues to stay on a black screen, close the 3ds lid and reopen it.

Sadly, that is the best I've got.

 

[3dsn00b]

http://gbatemp.net/threads/safea9lhinstaller.419577/ - here is how to do it

Yes, downloaded latest SafeA9LH and replaced my current arm9loaderhax.bin with the one from the zip by renaming the existing one to arm9loaderhaxold.bin. Put the payload files and the input files in the a9lh folder. SafeA9LH ran and updated successfully. Deleted the arm9loaderhax.bin renamed the old one back. Still no boot.

 

[linuxares]

So confusing... This is a LONG SHOT, have you tried Luma3DS Dev build?

 

[3dsn00b]

So confusing... This is a LONG SHOT, have you tried Luma3DS Dev build?

I haven't, but like I said, my suspicion is that it's a lot lower-level than software or sysNAND. I've pretty much given up on it for now. Maybe later when the community develops a pure arm9 updater I can try flashing original firmware to the sysNAND to rule out the sysNAND being corrupt. That still doesn't rule out a corrupt FIRM0 or FIRM1 and doesn't rule out a hardware fault. I'm ok with the mystery though, I've let it go tbh.

 

[kingaz]

I haven't, but like I said, my suspicion is that it's a lot lower-level than software or sysNAND. I've pretty much given up on it for now. Maybe later when the community develops a pure arm9 updater I can try flashing original firmware to the sysNAND to rule out the sysNAND being corrupt. That still doesn't rule out a corrupt FIRM0 or FIRM1 and doesn't rule out a hardware fault. I'm ok with the mystery though, I've let it go tbh.

Did you try my suggestion yet? On the chance that it's something weird happening with the screen init...

 

[3dsn00b]

Did you try my suggestion yet? On the chance that it's something weird happening with the screen init...

I did, unchecked Enable splash... left it for about 3 minutes, blue light was still on. Closed the lid, reopened. Nothing, no change.

 

[kingaz]

I did, unchecked Enable splash... left it for about 3 minutes, blue light was still on. Closed the lid, reopened. Nothing, no change.

Damn it! What happened to your 3ds?!?

 

[SnakeGS]

https://gbatemp.net/threads/help-black-screen-on-boot-a9hl-after-1-month-of-usage.423054/

TL;DR: I had a similar problem as you did, and I restored Sysnand, yet black screen. I sent to Nintendo under warranty period.

Today I got my console back.

The technical report says:

Synthom: Does not turn on;
Diagnosys: FPC Camera module broken - repaired under warranty;

Synthom: 3D Image Problem;
Diagnosys: Motherboard broken - repaired under warranty;

Synthom: Problem with the buttons;
Diagnosys: C-stick busted - repaired under warranty.

Note that I only sent because it did not turn on, and they repaired things I didn't even notice...
Nice work Nintendo!

So my thoughts, you have a defective board. My problem was the camera module, aparently, and when booting, since it didn't detect the camera, it would bootloop.

I think your best bet know is to send your N3DS for repairing if you do not have an hard mod.

Best regards!

 

[jatikeren]

Dont worry i got the same problem with you
the different is i dropped my O3DS and this happen..
perhaps motherboard is corrupt

 

[JCR1]

but the broken motherboard of 3dsnoob and snake was caused by the A9HL boot?

whatever, seems that is not possible restore a backup of your nand over corrupted nand without a hardmod!

 

[dubbz82]

https://github.com/AuroraWright/Luma3DS/commit/fef48a449a7662c8832099547d4b752da9c9c1e8

If this isn't actually a hardware problem...

 

[ertaboy356b]

Hi, I suggest you open your 3DS and try reseating the WIFI board.

 

[Xenon Hacks]

Hi, I suggest you open your 3DS and try reseating the WIFI board.

It's a N3DS there is no board just an antenna.