Homebrew ARM9Loader -- Technical Details and Discussion

  • Thread starter Thread starter Selver
  • Start date Start date
  • Views Views 579,203
  • Replies Replies 4,025
  • Likes Likes 42
Yeah, I get that being able to run D9 that early on will provide the ability to restore a working NAND backup if someone messes up sysNAND. I guess I just don't feel totally safe yet. It's not like the PSP where there was the Pandora battery, we can still get perma-bricked if enough shit went wrong. Always having my 9.2 sysNAND kinda gives me that protected feeling.
That's exactly why I'm keeping my 9.2 sysnand around for now. It stands like a sentinel, keeping me safe from the perils of vanilla nintendo updates and bricks alike. If emunand ever suffers a mortal blow, it will always be there to save the day and restore the emulated one to his former glory. XD
 
Last edited by FenrirWolf,
Can you clarify, are you saying there are two exploits by different authors and one has a brick bug?

Does the opt guide on GBA Temp install the buggoe arm9 build?

Hypothetical means not real. There's no known bug in a9lh, and the one from the otp guide (delebile's if i'm not mistaken) is perfectly fine.
 
  • Like
Reactions: democracy
Hey guys, if I recompiled my a9lh_installer can I safely reinstall it to a system with a working a9lh? Or I could potentially face a brick ?
 
I don't blame you. There's no compelling reason to do so yet. Even if emuNAND doesn't end up getting hooks for D9/E9, we can still just reboot into a boot manager and pick them once we have backlights and such.
I managed to confirm with punderino that you can restore SysNAND in Decrypt9 (from EmuNAND) somewhat successfully.
Granted, it's not a perfect test because I couldn't tell you why the restore was a frankenFIRM (was it the NAND restoration, or the attempt to inject A9LH FIRM1/0 after? The world may never know...)
However, it did bring the system's SysNAND from not booting at all (barring A9LH EmuNAND), to booting.

So D9 definitely works in 9.2 Emu, is what I'm saying.
I tested a read of SysNAND from it too, and that worked completely as expected.
 
Last edited by dkabot,
if I don't care enough about key dumping, other than faster emunand boot, what else would I gain from this? will booting cfw with this solve stable 3d bug?
 
if I don't care enough about key dumping, other than faster emunand boot, what else would I gain from this? will booting cfw with this solve stable 3d bug?
fixed 3d, being able to update and use sysnand and not having to fiddle with installing gba and dsi titles in two places, already having a9lh in place for future potential awesome things, not having to worry about menuhax failing on boot, etc
 
if I don't care enough about key dumping, other than faster emunand boot, what else would I gain from this? will booting cfw with this solve stable 3d bug?
1. In theory we would be able to load D9 to restore back up NANDS to help keep bricks to an all time low
2. Yes the 3d bug is fixed with A9LH
 
Screen stuff is going well, bilis fixed the top screen and I fixed the bottom screen... still needs backlight but that's all that's left...
look carefully you can read the text onscreen
OQgAsgF.jpg

backlight is next on the list :D
Amazing
 
I'm lost, what is this backlight?
*Sorry for noob question, first time hearing about this*
 
I'm lost, what is this backlight?
*Sorry for noob question, first time hearing about this*
People over at #cakey were trying to get screen init to work.

This means you can use Decrypt9 without the need of the 9.0-9.2 Firmware. This also means you can restore/backup your sysNAND without a hardmod, in case you brick it.

It seems like it's working now, which is great news!
 

Site & Scene News

Popular threads in this forum