Homebrew [RELEASE] The BootCTR9 release thread

Here is a first b9s 1.2 compatible dev build.

This dev-release only include a firm, since the .bin build is not yet running.

The next targes will be more code cleanup and getting the a9lh payload running again on a9lh.

I will also try to get the gateway payload running directly, but Gateway should maybe release a updated payload, since it should not be that hard for them.
 

Attachments

Here is a first b9s 1.2 compatible dev build.

This dev-release only include a firm, since the .bin build is not yet running.

The next targes will be more code cleanup and getting the a9lh payload running again on a9lh.

I will also try to get the gateway payload running directly, but Gateway should maybe release a updated payload, since it should not be that hard for them.

how did you convert it to work with 1.2? i tried the new firmtool and it doesn't work at all ( gives the arm9 error with the dump happening)
 
how did you convert it to work with 1.2? i tried the new firmtool and it doesn't work at all ( gives the arm9 error with the dump happening)
The framebuffer handling changed, they are now passed as argument, so you need to get them there, or you need an arm11 payload which reads them directly from the config registers, otherwise its possible that you try to write to an invalid address.
Payloads loaded with BootCTR9 should not have this problem, since I'm setting up the cake and gateway framebuffer pointers.
 
The framebuffer handling changed, they are now passed as argument, so you need to get them there, or you need an arm11 payload which reads them directly from the config registers, otherwise its possible that you try to write to an invalid address.
Payloads loaded with BootCTR9 should not have this problem, since I'm setting up the cake and gateway framebuffer pointers.

so when we use the command line "firmtool build test.firm -n 0x23F00000 -e 0 -D mypayload.bin -A 0x23F00000 -C NDMA" this doesn't work because we need to change the 0x23F00000?
 
so when we use the command line "firmtool build test.firm -n 0x23F00000 -e 0 -D mypayload.bin -A 0x23F00000 -C NDMA" this doesn't work because we need to change the 0x23F00000?
No, the firm tool is not enougth, you could add a stub arm11 payload which could setup the cake framebuffers from the config registers, or the payload itself needs to be modified.
Most payloads directly use cakehax framebuffer addresses at 0x23FFFE00-0x23FFFE08, but since they are no longer set in b9s, because they are now passed as an argument, there are pointig to an invalid address. when the payloads then trys to write to this address, because they want to show something, the exception happens.
 
animation is so fluid now D:

--------------------- MERGED ---------------------------

can't wait for bottom screen animation support
 
Just wanted to throw my hat on the pile of successful BootCTR9 setups.
Got a nice boot animation over top of my existing Luma bootsplash.
It's a long boot time, but 1. I rarely reboot my 3DS anyway, and 2. the load screen says "take your time" for a reason.
If anyone wants the anim file, I'll throw it on my webspace. Just let me know.
 
Just wanted to throw my hat on the pile of successful BootCTR9 setups.
Got a nice boot animation over top of my existing Luma bootsplash.
It's a long boot time, but 1. I rarely reboot my 3DS anyway, and 2. the load screen says "take your time" for a reason.
If anyone wants the anim file, I'll throw it on my webspace. Just let me know.
Is the ASCII splash intentional? It throws me off tbh.
 
Here is a first b9s 1.2 compatible dev build.

This dev-release only include a firm, since the .bin build is not yet running.

The next targes will be more code cleanup and getting the a9lh payload running again on a9lh.

I will also try to get the gateway payload running directly, but Gateway should maybe release a updated payload, since it should not be that hard for them.
The previous build is working perfectly with b9s 1.2, for me. Is there any point in updating?
 
Here is a first b9s 1.2 compatible dev build.

This dev-release only include a firm, since the .bin build is not yet running.

The next targes will be more code cleanup and getting the a9lh payload running again on a9lh.

I will also try to get the gateway payload running directly, but Gateway should maybe release a updated payload, since it should not be that hard for them.

Works like a dream for Gateway loading. Thank you!
 
Here is a first b9s 1.2 compatible dev build.

This dev-release only include a firm, since the .bin build is not yet running.

The next targes will be more code cleanup and getting the a9lh payload running again on a9lh.

I will also try to get the gateway payload running directly, but Gateway should maybe release a updated payload, since it should not be that hard for them.
thank you, works fine again. i hope they finish putting out updates that completely breaks compatibility..
 
Well I was able to get the may 3rd nightly of skieth to work and the dat/bin version of cakes to work.I was wondering if there was a way to hide the bootctr9 screen that pops up before the animations so I can get a cleaner look?
 
Well I was able to get the may 3rd nightly of skieth to work and the dat/bin version of cakes to work.I was wondering if there was a way to hide the bootctr9 screen that pops up before the animations so I can get a cleaner look?
You just need to set the boot splash in the main configuration to 0 to disable it, as it is documented here :)
 

Site & Scene News

Popular threads in this forum