Homebrew ARM9Loader -- Technical Details and Discussion

[Shadowtrance]

Currenty both Decrypt9UI (posted and compiled by Shadowtrance) and Decrypt9WIP (compiled by me) work with A9LH. Although yeah, Shadowtrance's is the minimal one.

Both versions are in mine too btw. (still both minimal though)

 

[subcon959]

Both versions are in mine too btw. (still both minimal though)

Is it normal for it to take a loooong time for the bottom screen to appear on your minimal version when using a 128GB msd?

 

[Yudowat]

this might not be the correct procedure on new 3ds

This is pretty much exactly what I did on my N3DS XL so there you go! But some people are still having the issue with nothing displaying I think

 

[Shadowtrance]

Is it normal for it to take a loooong time for the bottom screen to appear on your minimal version when using a 128GB msd?

No idea, don't have a 128gb card to test.
Works fine on my 32gb cards though.

 

[PixelBurst]

well, thanks to bilis for all his help and answering all of my noob questions, and for his screen init code and other code and stuff he's provided me that's made all of this possible, we now have a nice installer... get it while it's hot guys

directions: run the installer with the provided stage0x5C000 from your EXISTING arm9loaderhax install

N3DS worked fine with the update you provided, mine was originally created from delebile build. Saw you say the screen glitchyness was fixed on your repo, do I need to use your files to recompile to fix it, or is this something that could be fixed in an update as well? Thanks for all your work on this.

Once I've dealt with this glitchness, I'll be getting rid of emunand. Backups stored on cloud in case anything goes wrong, but I can boot into D9 from boot thanks to the modified CTR, and Aureinand works great!

 

[runetoonxx2]

Soo what page is the newest screen init on IMA update

 

[Housey]

For me, having a splash.bin or not takes the same amount of time with the new update.

Still about 10.2 seconds to coldboot into emunand which is p. amazing!

 

[subcon959]

No idea, don't have a 128gb card to test.
Works fine on my 32gb cards though.

It takes less than a second from power on for the top screen to appear, but then what feels like 30 seconds for the bottom screen.

I'm gonna transfer everything to a smaller card and test.

 

[Supster131]

For me, having a splash.bin or not takes the same amount of time with the new update.

Still about 10.2 seconds to coldboot into emunand which is p. amazing!

Yeah, not sure if it's a placebo effect, but even with a splash image, it feels like my sysNAND boots like a second or two quicker with dark samus' build. (I have yet to actually time it though, so it can most likely be a placebo )

 

[Shadowtrance]

It takes less than a second from power on for the top screen to appear, but then what feels like 30 seconds for the bottom screen.

I'm gonna transfer everything to a smaller card and test.

I could be the sd card size check that happens on start up which then gets displayed on the top screen. Other than that i can't think of why it would be slow. Sometimes that check can be slow, not much can be done about it.

 

[Audioboxer]

Whatever decrypt9 version I downloaded loaded pretty much instantly on my 128GB card. It's a samsung class 10.

 

[Mrrraou]

Yeah, not sure if it's a placebo effect, but even with a splash image, it feels like my sysNAND boots like a second or two quicker with dark samus' build. (I have yet to actually time it though, so it can most likely be a placebo )

Placebo, it should even be a bit slower.

 

[Supster131]

Placebo, it should even be a bit slower.

My placebo can't be that strong, can it? I'll time it once I get home.

Original A9LH booted sysNAND in like 9-10 seconds.

 

[Noroxus]

Would anyone be so kind as to upload a video of the boot decrypt9? I would love to see how it looks like

 

[PixelBurst]

Does anyone know if its safe to just compile dark_samus3's arm9loaderhax with my own OTP again and install over a delebile installed arm9loaderhax? I assume as it just writes to firm0 and firm1 again it should be safe, but wanted to make sure as I don't have a hardmod if it hits the fan.

 

[subcon959]

Does anyone know if its safe to just compile dark_samus3's arm9loaderhax with my own OTP again and install over a delebile installed arm9loaderhax? I assume as it just writes to firm0 and firm1 again it should be safe, but wanted to make sure as I don't have a hardmod if it hits the fan.

It's safe, I've done it several times now.

 

[dkabot]

Would anyone be so kind as to upload a video of the boot decrypt9? I would love to see how it looks like

Well it's been a lot of work, but thanks to all of the hard work done we now have screeninit integrated into the stage2 payload

video: http://www.mediafire.com/watch/49sv4qbnbiic0j0/VID_20160225_013731.mp4

sorry for crappy camera work but it was all I could do... this is currently being cleaned up and then there'll be a pull request to delebile's repo

Watch that, gives an example of what it's like

Does anyone know if its safe to just compile dark_samus3's arm9loaderhax with my own OTP again and install over a delebile installed arm9loaderhax? I assume as it just writes to firm0 and firm1 again it should be safe, but wanted to make sure as I don't have a hardmod if it hits the fan.

I'd recommend the updater, personally, but compiling the branch and reinstalling works too.

 

[PixelBurst]

It's safe, I've done it several times now.

Thanks a lot, just compiled it so will do it myself now. No more glitchy screen then cfw sysnand masterrace here I come!

 

[otto888]

I'm also having screen init issues on a N3DS XL. It's 9.2E. My 9.0U N3DSXL displays just fine. Can I just put the old stage0x5C000.bin from my initial install on the SD root and have it overwrite the new one? Or should I just do a new install? Want to go back to intiless exploit on the E unit until it's fixed.

 

[dkabot]

I'm also having screen init issues on a N3DS XL. It's 9.2E. My 9.0U N3DSXL displays just fine. Can I just put the old stage0x5C000.bin from my initial install on the SD root and have it overwrite the new one? Or should I just do a new install? Want to go back to intiless exploit on the E unit until it's fixed.

If you have issues with your screen init after it was successfully installed, I would suggest:

• Making sure whatever you're using as a payload (ie AuRei) is up to date.
• Asking in IRC or something about the issues, if you have time.

Otherwise, a reinstall from repo would work, can't speak as to if the updater would.