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.
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!
opt.bin -> otp0x108.bin: failed!
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.
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.
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.
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."
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."
Last edited by linuxares,
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.
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.
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.
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...
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:
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!
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:
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!
Dont worry i got the same problem with you
the different is i dropped my O3DS and this happen..
perhaps motherboard is corrupt
the different is i dropped my O3DS and this happen..
perhaps motherboard is corrupt
https://github.com/AuroraWright/Luma3DS/commit/fef48a449a7662c8832099547d4b752da9c9c1e8
If this isn't actually a hardware problem...
If this isn't actually a hardware problem...
Similar threads
- Question
- No one is chatting at the moment.
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
-
