Hacking Official [Source Release] ReiNand CFW

  • Thread starter Thread starter Reisyukaku
  • Start date Start date
  • Views Views 993,087
  • Replies Replies 6,480
  • Likes Likes 115
It's a bug on all 3DS's, old and new.
This bug is an emuNAND issue and not a reiNAND issue, from what I'm aware at least.
Please do research before anwsering please :D, The 3D Bug issue is only for New 3ds'es and its being caused by the face tracking feature,Team SALT Has fixed it already but they never releases there code.
 
  • Like
Reactions: cearp and gp1993
Please do research before anwsering please :D, The 3D Bug issue is only for New 3ds'es and its being caused by the face tracking feature,Team SALT Has fixed it already but they never releases there code.
Read the last part I said in my sentence, it's what I've been told, so that's what I said.
 
It's a bug on all 3DS's, old and new.
This bug is an emuNAND issue and not a reiNAND issue, from what I'm aware at least.

do you know this bug or glitch is common with n3ds ? or this is only for a few 3ds's ?
what do you think about a future patch ? will that fixed by next update(s) of reinand ?
thanks

It's a N3DS issue only from what I understand. It has to do with a dirty re-initialization of the display (specifically the parallax barrier from what I remember) during the launch of emunand. Supposedly the SALT/KARL team fixed this issue with their private cfw by doing a complete shut down of the display and initializing it as if from a clean boot. There was a thread a while ago about it that was recently necro'd and a member of SALT replied after the necro with a rather detailed explanation of how they fixed it.
 
It's a N3DS issue only from what I understand. It has to do with a dirty re-initialization of the display (specifically the parallax barrier from what I remember) during the launch of emunand. Supposedly the SALT/KARL team fixed this issue with their private cfw by doing a complete shut down of the display and initializing it as if from a clean boot. There was a thread a while ago about it that was recently necro'd and a member of SALT replied after the necro with a rather detailed explanation of how they fixed it.
Thanks for clearing that up properly :P Sorry about my mistake.
 
  • Like
Reactions: gp1993
I almost wonder if we could just make a simple call to gsp::LCD to turn the displays off after the splash screen and then let the kernel (i.e. firmware.bin) turn it back on. I doubt it's that simple though.
 
Thanks for clearing that up properly :P Sorry about my mistake.

I almost wonder if we could just make a simple call to gsp::LCD to turn the displays off after the splash screen and then let the kernel (i.e. firmware.bin) turn it back on. I doubt it's that simple though.

Here is the post from @WulfyStylez about what they did to fix it. Nothing overly technical, but I would assume anyone with a working knowledge of the 3ds and coding a cfw would be able to figure out how to apply his general explanation to a fix in the code. Though, as someone else pointed out, it would help if they would post the code for their project...

https://gbatemp.net/threads/lost-super-stable-3d.388046/page-2#post-6027267
 
  • Like
Reactions: prototech
Here is the post from @WulfyStylez about what they did to fix it. Nothing overly technical, but I would assume anyone with a working knowledge of the 3ds and coding a cfw would be able to figure out how to apply his general explanation to a fix in the code. Though, as someone else pointed out, it would help if they would post the code for their project...

https://gbatemp.net/threads/lost-super-stable-3d.388046/page-2#post-6027267
How come they never released their code for it?
 
How come they never released their code for it?

It's a long story, but from what I remember, they had sort of planned on releasing it, but then at some point decided not to after drama and whining from some people, then it turned into show-off videos, and then nothing after that.

I'm just glad Wulfy shared some of the details in that other thread. SALT may not release a lot, but they do release details on some things, which is always appreciated.
 
It's a long story, but from what I remember, they had sort of planned on releasing it, but then at some point decided not to after drama and whining from some people, then it turned into show-off videos, and then nothing after that.

I'm just glad Wulfy shared some of the details in that other thread. SALT may not release a lot, but they do release details on some things, which is always appreciated.
There's a reason they're called salt. Truth be told, I always believe they'd look for a reason not to release something.

Anyway, that's a pretty fair amount of information.
 
  • Like
Reactions: daxtsu
It's a long story, but from what I remember, they had sort of planned on releasing it, but then at some point decided not to after drama and whining from some people, then it turned into show-off videos, and then nothing after that.

I'm just glad Wulfy shared some of the details in that other thread. SALT may not release a lot, but they do release details on some things, which is always appreciated.

To be fair, they kinda earned/deserved the flack they got during the KARL project. They were acting very high and mighty about how they would not do anything to allow/enable piracy and would in fact actively try to prevent the use of their code for piracy. Yet it certainly appears as if that little qualm went out the window they second they stopped acting as if they planned to release something publicly.

In all honestly I fully believe they never had any intention of releasing any code, solely because of how vocal they were about being "anti-piracy". You can't exactly release source code and not have someone edit it to remove the signature checks.

edit:

Don't get me wrong, I am extremely grateful to those members of the team like @WulfyStylez who actually DO offer advice and assistance to the greater community in regards to solving certain issues that arise in cfw. But the team has a whole are jerks and show offs who are indicative of why certain dev/hacking scenes lately have been stagnant. If you have something that is an improvement in ANY way over the mean standard for the community, you should release it. At the very least help guide the community towards accomplishing it rather than lording it over them that you did something they can't figure out.

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

Before this devolves into an argument about "entitlement" and how devs have no obligation to release anything (like the Wii U threads lately), let me just state for the record that I by no means feel entitled to anything anyone else discovers or develops. Devs and teams like Gateway, Reisyukaku, Roxas, Pasta, Smealum and the like are the ONLY reason we have any sort of scene and they did a lot of hard work to get us here. I am extremely grateful for that.

That said, it is impossible for a scene to exist or expand when people or teams who find things like arm9 exploits/entrypoints keep them hidden away for their own personal use. It is one thing when they simply hold onto an exploit because it is the ONLY exploit and they dont want to risk a patch yet (like Marionumber1 did for the Wii U and like yls8 does for his webkit exploits). There is a distinct difference between what they have done and what teams like SALT are doing. An argument could easily be made that SALT is negatively impacting the 3ds scene by keeping their exploit private.
 
Last edited by Aroth,
An argument could easily be made that SALT is negatively impacting the 3ds scene by keeping their exploit private.
'Their' exploit isn't private anymore, though, they were using arm9loaderhax in their most recent demo video, and delebile released his implementation of that. Before that, firmlaunchhax was public long before they showed any inclination towards a release. And now with the N3DS keystore public, there's nothing left to prevent piracy by not releasing. Showing off is more appealing to them, I guess.
 
Please do research before anwsering please :D, The 3D Bug issue is only for New 3ds'es and its being caused by the face tracking feature,Team SALT Has fixed it already but they never releases there code.
so how we can fix that ? only one way ? closing and opening n3ds'es ?
thanks you
 
so how we can fix that ? only one way ? closing and opening n3ds'es ?
thanks you

Basically yes. Close the lid then wait a second and reopen it.

That or learn how to code and implement a fix to one of the existing CFW's that does what Wulfy describes to permanently solve the problem.

Though I suspect that SALT was only able to "fix" the problem because of the nature of the arm9loaderhax exploit.
 
  • Like
Reactions: klear and gp1993
so how we can fix that ? only one way ? closing and opening n3ds'es ?
thanks you

It's mostly up to the CFW developers, but basically, the code has to reset the screen and GPU into a state where it's as if you're turning the 3DS on from a cold boot. Right now, no public CFW does that, which causes the screen to get glitchy.
 
  • Like
Reactions: klear and gp1993

Site & Scene News

Popular threads in this forum