Hacking Official [Release] CakesFW

  • Thread starter Thread starter mid-kid
  • Start date Start date
  • Views Views 842,424
  • Replies Replies 3,542
  • Likes Likes 73
So I'm using sysNAND 4.2U and emuNAND 10.5U on an o3DS XL, and I've had no problems with Cakes up until now.
I've been using Cakes 102 and decided to update to 108, but it boots to a black screen.
I've enabled the 7.x NCCH patches option, and eventually just redownloaded everything but nothing's worked.

I can go back to 102 and have everything working just fine, but what can I do to use 108?

https://github.com/mid-kid/CakesForeveryWan/commit/778f887a492aca73aeae4bc3259c5a1cd8905a1b
Get the slot0x25keyX cakes from nightly 131 once it's built, they're usable with 108.
 
Last edited by mid-kid,
"The firmware.bin you're trying to use is most probably not supported by cakes"

That's bullshit, there are only two available as far as I know, one for O3DS and one for N3DS. Why isn't this working? I'm on a N3DS, by the way.
 
"The firmware.bin you're trying to use is most probably not supported by cakes"

That's bullshit, there are only two available as far as I know, one for O3DS and one for N3DS. Why isn't this working? I'm on a N3DS, by the way.
There are multiple versions of each that correspond to the versions of NATIVE_FIRM (firmware.bin is NATIVE_FIRM as I understand it); you can find a list of all the different ones here, just hover over the v##### to see which firmware that version was introduced with. For instance, o3DS NATIVE_FIRM v20262 was introduced with 9.6, and it's the one you need to use with Cakes stable (108) if you're on o3DS.

If you're using Cakes stable, the appropriate versions are: o3DS, n3DS. As far as I know, these will also work on newer versions of Cakes, but newer versions of Cakes also support newer versions of NATIVE_FIRM, which you should use instead of the ones I just linked if they're supported. I think the latest build supports 10.4 NATIVE_FIRM, but don't quote me on that.
 
  • Like
Reactions: Zidapi
These will also work on newer versions of Cakes, but newer versions of Cakes also support newer versions of NATIVE_FIRM, which you could use instead of the ones I just linked if they're supported.
Fixed that for you. The recommended version is always the one linked in the OP.
 
  • Like
Reactions: twocows
I have a problem with cakesFW r129
My N3ds freezes at "Loading Cakes"...

Mounted SD Card
Loading NATIV_FIRM...
Loaded FIRM
Loaded FIRM key
.
.
.
Loading AGB_FIRM
Failed to load FIRM
Loading Cakes

3DS freezes
 
I have a problem with cakesFW r129
My N3ds freezes at "Loading Cakes"...

Mounted SD Card
Loading NATIV_FIRM...
Loaded FIRM
Loaded FIRM key
.
.
.
Loading AGB_FIRM
Failed to load FIRM
Loading Cakes

3DS freezes

Look a page back, trying to fix it (struggling to install a9lh), while keeping support for a9lh.
 
Last edited by mid-kid,
Look a page back, trying to fix it (struggling to install a9lh), while keeping support for a9lh.

131 supports a9lh now, or are you referring to the fork you posted a few pages back? Also, can one just copy build/main.bin and rename it to arm9loaderhax.bin after building normally, or do we really need to run make build/main.bin and rename the file? I guess I can compare the two with hash checks and see for myself.
 
131 supports a9lh now, or are you referring to the fork you posted a few pages back?
No, well, kind of. The draw functions will fuck up due to the framebuffers not being available, but the MPU setup works.

Also, can one just copy build/main.bin and rename it to arm9loaderhax.bin after building normally, or do we really need to run make build/main.bin and rename the file? I guess I can compare the two with hash checks and see for myself.
The target all (the default one), requires launcher, which requires out/Cakes.dat, which requires build/main.bin, so yes.
 
Hi guys I'm confused trying to get the CFW to run as a whole. Whenever I try to run it through the Homebrew Launcher (which I get to through CtrBootManager), I get a black screen. I scanned the QR code and the page just said "Loading code.bin". Not sure what else I'm supposed to do after that. I left the page open for around a minute, and then I rebooted my 3DS into the Hombrew Menu, tried to run Cakes, and got a black screen. I was using ReiNAND CFW before, and I am on the latest emunand CFW version (10.5) on my New 3DS XL. My Sysnand is on 9.2.0-20U.

Attached are pictures of my microSD card setup. Any help is appreciated.
a5c9a7fa2ef8caf8404f0cecbc553467.png
8b660652c9800ada2ad64c1c1de186d0.png
0c1b09ed71f4799533807892d9e5cdcb.png
 
Hi guys I'm confused trying to get the CFW to run as a whole. Whenever I try to run it through the Homebrew Launcher (which I get to through CtrBootManager), I get a black screen. I scanned the QR code and the page just said "Loading code.bin". Not sure what else I'm supposed to do after that. I left the page open for around a minute, and then I rebooted my 3DS into the Hombrew Menu, tried to run Cakes, and got a black screen. I was using ReiNAND CFW before, and I am on the latest emunand CFW version (10.5) on my New 3DS XL. My Sysnand is on 9.2.0-20U.

Attached are pictures of my microSD card setup. Any help is appreciated.
a5c9a7fa2ef8caf8404f0cecbc553467.png
8b660652c9800ada2ad64c1c1de186d0.png
0c1b09ed71f4799533807892d9e5cdcb.png
You can't use the old3DS browser exploit to launch cakesFW on your new3ds, which is what it sounds like you're trying to do.
 
You can't use the old3DS browser exploit to launch cakesFW on your new3ds, which is what it sounds like you're trying to do.
I thought I had to "install" it through the browser, and then go to the homebrew channel to launch it. I am trying to just run the cfw as a whole. When I launch it through the homebrew channel, it just takes me to a black screen.
 
Last edited by Lazyjones,
I too am getting a black screen upon booting cakes (O3DS 4.5/10.5) using the DS Profile.

Are there multiple versions of slot0x25keyX? So far I only managed to find one (MD5s match).

Edit: Got it to work by using the patches from the 131 release.
Sorry for the slight inconvenience. I just never got made aware of this bug until now (which took pretty darn long).
Will release a new stable soon™ after some things with a9lh are worked out.
 
  • Like
Reactions: leerz

Site & Scene News

Popular threads in this forum