Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by mid-kid, Jun 20, 2015.
i don't know what i need to do now, i cant hardmod for a dowgrade right?
You can only downgrade if you have a NAND backup from before 11.3
11.3 patched out all software downgrades, as well added a NATIVE_FIRM requirement to the homemenu. This basically made hardmod/dsiware downgrade impossible to do.
1- Download http://chunk.io/f/014612541fa04235a6f7593c86a4a200.3dsx
2- Rename 014612541fa04235a6f7593c86a4a200.3dsx to Cakes.3dsx and overwrite your Cakes.3dsx on 3ds
3- Launch cakes from Homebrew Launcher
When i unlocked my 3ds first time i did a nand backup, now i need to search . thanks
black screen 4evar :/
I updated to 11.3 and got black screen. I believe I am on arm9loaderhax and was on older version of cakes. I think I replaced all the proper files. Held L to get into CakesFW190 options. Set options Block FIRM..., Survive reboots..., Disable signature checks.
I select Boot CFW and get a black screen.
Bottom screen debug log is
Loaded config file
Loading NATIVE_FIRM. . .
FIRM seems not encrypted
ARM9 FIRM binary seems not encrypted
Fixing arm9 entrypoint. . .
Loading TWL_FIRM. . .
Failed to load FIRM
Loading AGB_FIRM. . .
Failed to load FIRM
Loaded selected cakes
any help appreciated.
edit: I'm not sure what I was doing wrong. Probably my fault with all the different guides out and not being completely up to date with info but I ended switching to Luma. Replaced the arm9loaderhax.bin with the latest Luma3D github release and it booted into Luma options and then I could boot into 3ds menu and games. Thanks to all the devs always.
That will not work, they updated without the FIRM protection turned on and removed their A9LH. There is no way to boot into a CakeFW with OFW 11.3
Do you have DsWiFiPWN installed?
Edit: I mean the guy who updated without the FIRM patches
So it appears your 3ds_injector actually doesn't work on 11.3. I made a mistake during my testing and completely overlooked this issue until I did further testing.
The version I built into my pack does work - at least the regionfree patch!
Not sure if I just took the 11.1/2 version and hacked the recipe to declare it as 11.3-kernel compatible (probably yes since I also already changed /injector to /cakes/injector) or I actually redownloaded the sources, but I'm running 11.3 and can run nico nico douga
Double checked, yep I used his 11.1 version and added 11.3 support, "Jerry-Shaw" on github actually posted one
Tested out out patch and it is indeed working
It looks like when I was doing my tests, I accidentally booted into the CFW on my CTRNAND instead of CakesFW.
I just made little changes to the fork from @Wolfvak . Thanks to @Wolfvak and @mid-kid . Really need region free. What's more, I moved some paths from the root to cakes folder instead for better controlling.
— Posts automatically merged - Please don't double post! —
BTW, is there anyone knowing what is "switching out nand header first..." when doing ctrnand transfer to 2.1 on N3DS, since I cannot find the otpless guide now.
One of my friends met this problem, and can do nothing on hacking to A9LH.
Quick question, probably already been asked, but if I use an older TWL_FIRM and older AGB_FIRM with a newer NATIVE_FIRM will i brick?
Sent from my iPhone using Tapatalk
11.4 has been released and it appears to add a new NATIVE_FIRM. So chances are CakesFW will need an update as well.
Wait for update. Seems like all new firmware in the future will check NATIVE_FIRM from 11.3.
Just checked, can boot on CakesFW Ver190, but cannot go any further.
I've been made aware of the 11.4 update. I will update CakesFW later today.
Is there anyway for us to get the hash of firm's section of any new firmware.bin? So that we could add new NATIVE_FIRM support ourselves. I tried but failed since I am not good at C anyway.
The gist of it is: You decrypt the FIRM you downloaded from the CDN (CakesFW gives you a decrypted copy as firmware_unsupported.bin), then you get the first 0x10 bytes of the hash of the first section as according to this, which means bytes 0x50-0x60 in a hex editor.
That's just to make Cakes recognize the FIRM however, you need to adapt one or two more parts of the code that do different things for different versions (most notably in boot_firm()), and port all the patches.
If you need any further help, you're always welcome to ping me on #Cakey on freenode IRC.
Haha, thank you so much. I was stucked here in getting the hash right now. As for following code, I think I could manage to get over it.
Oops... Freenode IRC seems not to be available in my country...