Hacking FAQ about 3ds system update 11.3

  • Thread starter Thread starter Sketchy1
  • Start date Start date
  • Views Views 33,949
  • Replies Replies 181
  • Likes Likes 21
I updated my emunand to 11.3 and now i only get a black screen after try to boot.
CFW: Luma3DS 6.6
 
If you're on 11.2 or below, you can.
If you're on 11.3, smea updated the payloads to work on 11.3, so you would be able to launch the homebrew launcher, but we don't have any kernelhax on 11.3.

To sum up:
If you are on 11.3, you can only use homebrew, not CFW at the moment

but my homebrew won't launch. it says error & restart system or something like that
 
Because the new payloads are a bit different from the older ones, some entrypoints need to be updated

this is what i get. Smea tweeted that its okay now but some people were tweeting him this same error. he says its fine though as of yesterday
 

Attachments

  • IMG_5622.JPG
    IMG_5622.JPG
    1 MB · Views: 203
It is, yes, but smea updated his payloads, if you rename them, you can restore basic userland homebrew but cannot downgrade though.

How do I rename them? I see no 'hblauncherloader' folder.

Edit: nevermind, I created one myself, downloaded the ropbin payloads and worked.
 
Last edited by pustal,
this is what i get. Smea tweeted that its okay now but some people were tweeting him this same error. he says its fine though as of yesterday
What entrypoint are you using?
I heard oothax and the homebrew launcher loader works, I'm not sure about soundhax though
 
I had a 4.4 vanilla o3ds that i used for a supercardDStwo DS gaming only.
I updated it yesterday to 11.3 a9lh+luma following plailects guide.

Everything is working fine w .cia files, homebrew and such, but the DStwo card is NO longer recognized in the o3ds. How do I get the 3ds to see it again??
The card is not damaged, it still works on my other n3ds w 9.2 sysnand that I use for GW emunand stuff. What the heck is the issue?
 
I had a 4.4 vanilla o3ds that i used for a supercardDStwo DS gaming only.
I updated it yesterday to 11.3 a9lh+luma following plailects guide.

Everything is working fine w .cia files, homebrew and such, but the DStwo card is NO longer recognized in the o3ds. How do I get the 3ds to see it again??
The card is not damaged, it still works on my other n3ds w 9.2 sysnand that I use for GW emunand stuff. What the heck is the issue?

Maybe the flashcart is blocked by the update?
 
Well that's my guess too, but I thought luma somehow prevents card blocking from happening. I could've sworn I read others saying they were fine on 11.3.
 
Maybe a dumb question but i see that downgrading is not possible anymore with 11.3. Is that only when you have ofw? Or also with cfw?
Say i want to restore a nand that is 11.2 is that still possible or is that also blocked?
 
Maybe a dumb question but i see that downgrading is not possible anymore with 11.3. Is that only when you have ofw? Or also with cfw?
Say i want to restore a nand that is 11.2 is that still possible or is that also blocked?
If you have an 11.2 NAND backup, you can restore it using hourglass9. You won't suffer any negative effects from doing so. That's one the great benefits to being able to backup/restore your NANDs. Because those features trigger before the NAND has a chance to boot, you basically avoid any real means of Nintendo blocking you.
 
So can I update to 11.3, then restore my 11.2 NAND so that I'm still considered on 11.3, but have the firmware of 11.2?
No, that's not how NANDs work. If you restore your 11.2 NAND, it completely overwrites the current NAND.
 
  • Like
Reactions: NintendoFan06
Wow. such confusion.

If you use 3ds.guides instructions, and install working arm9hax, and then restore your OFW backup, you ARE SAFE TO UPDATE SYSNAND TO 11.3. You will then be running 11.3 custom luna3ds SYSnand.

when a new OFW shows up, wait until the lumacfw is confirmed to work before updating. from what i understand it's supposed to just work and there's nothing nintendo can do because luma protects the part with arm9hax, but there's no guarantee that the NEXT OFW won't break Luma somehow.

If the version after 11.3 somehow breaks cfw and you are trying to bleeding edge, well, that's why you nand backup first so you can go back to 11.3.
 
Wow. such confusion.

If you use 3ds.guides instructions, and install working arm9hax, and then restore your OFW backup, you ARE SAFE TO UPDATE SYSNAND TO 11.3. You will then be running 11.3 custom luna3ds SYSnand.

when a new OFW shows up, wait until the lumacfw is confirmed to work before updating. from what i understand it's supposed to just work and there's nothing nintendo can do because luma protects the part with arm9hax, but there's no guarantee that the NEXT OFW won't break Luma somehow.

If the version after 11.3 somehow breaks cfw and you are trying to bleeding edge, well, that's why you nand backup first so you can go back to 11.3.
What?
The only reasons 11.3 caused issues for CFWs, is because of the NATIVE_FIRM requirement they added to the homemenu. Otherwise the system was still ultimately protected.
Also Luma3DS isn't the only CFW
 
Last edited by The Catboy,

Site & Scene News

Popular threads in this forum