Hacking RELEASE [Official] ReiNX thread [DEAD]

[TotalInsanity4]

No it is not! It is only naehrwert's hwinit code. The rest of this CFW are only binary blobs.

https://github.com/Reisyukaku/ReiNX?files=1

?

 

[jakkal]

@Reisyukaku
Will this remain a closed source project?

Wow lol

 

[tecfreak]

It's open-source. The only thing that's closed-source (for now) is the signature patches, and I think that's because Reisyukaku doesn't want someone forking them into a renamed CFW that overshadows ReiNX before they're done.

I'm curious if it really ever become open source.

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

https://github.com/Reisyukaku/ReiNX?files=1

?

Wow lol

Well, then explain this to me you smartass:
https://github.com/Reisyukaku/ReiNX/tree/master/data

 

[dkabot]

https://github.com/Reisyukaku/ReiNX?files=1

?

https://github.com/Reisyukaku/ReiNX/tree/master/data
I believe it's about the `.kip` files, which just sit there and get copied.

 

[Darth Meteos]

I'm curious if it really ever become open source.

you are the best part of our voice chat right now, keep going

I would compile it with sig check patches baked in, but not release it.... Not at all hard to do, but of course,someone would fudge it all.

making it work at all is the real issue. we've been trying it on everyone's switch, and it's just not playing nice right now.

 

[Subtle Demise]

The unpack apparently fixed that, it just turns out and idiot with pirated IDA Pro still has no idea what they're doing.
Those that do (Rei) managed to see everything just fine.

Just because it's decrypted, the code can still be needlessly complex and filled with red herrings. The fact that you can never get actual commented source code from "decompiling" the binaries makes obfuscation trivial, even for those doing it non-professionaly. Devolution still doesn't have the anti-piracy checks patched out, despite being a homebrew for possibly the most cracked-open console ever.

Now unless I'm wrong and one of them have said that they see how the patching works, and either won't or can't implement it for some reason or another, it's still obviously not as simple as a copy+paste operation.

 

[Lacius]

I'm curious if it really ever become open source.

Once everything is working properly and ReiNX is officially released (and not a work-in-progress), I don't see why it wouldn't be truly open-source.

I do admit that the fact that it's not already is a little disconcerting. Reisyukaku expressed an interest in making this WIP release in part for extra assistance with time-consuming work, but obfuscating the kip files and the work on signature patches seems counterproductive with regard to that previously stated goal.

 

[TotalInsanity4]

https://github.com/Reisyukaku/ReiNX/tree/master/data
I believe it's about the `.kip` files, which just sit there and get copied.

Mm, I guess that makes sense. The actual firmware code is very much visible, though

 

[Subtle Demise]

If this is the case Rei will have to fix this because we will need exfat once .xci and .nsps are working. Please correct me if im wrong!

Not necessarily, PS3 CFWs and backup loaders had support for split files on fat32 external drives.

 

[gothteen]

I'm curious if it really ever become open source.

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

Well, then explain this to me you smartass:
https://github.com/Reisyukaku/ReiNX/tree/master/data

Are these guys for real.... Come on guys, compile the cfw, build a bin for yourself and try it out. Its our very first CFW ^^ Happy days allright! Anyways, Rei allready stated a million times before, like so many others the cfw is a WIP, this means Work In Progress... (S)he is not done, he hasnt closed the software or anything (open source ftw) and sig patches are coming asap. Give it some time and i think we all will be running reinx in one way or another in about 2 months.

Again, great job on publising the code rei, we love it And dont bother about the flamers, a guy has to complain after all things said and done apparently

 

[Phenj]

compiled version?

 

[Lacius]

Just because it's decrypted, the code can still be needlessly complex and filled with red herrings. The fact that you can never get actual commented source code from "decompiling" the binaries makes obfuscation trivial, even for those doing it non-professionaly. Devolution still doesn't have the anti-piracy checks patched out, despite being a homebrew for possibly the most cracked-open console ever.

Now unless I'm wrong and one of them have said that they see how the patching works, and either won't or can't implement it for some reason or another, it's still obviously not as simple as a copy+paste operation.

You're mostly correct. The easier thing to do is to take the few features that make SX OS worth anything and implement them in an open-source CFW.

The more difficult task of cracking SX OS is a challenge in of itself, but most people who have the skills and the desire to do so aren't going to release it.

 

[dkabot]

Just because it's decrypted, the code can still be needlessly complex and filled with red herrings. The fact that you can never get actual commented source code from "decompiling" the binaries makes obfuscation trivial, even for those doing it non-professionaly. Devolution still doesn't have the anti-piracy checks patched out, despite being a homebrew for possibly the most cracked-open console ever.

Now unless I'm wrong and one of them have said that they see how the patching works, and either won't or can't implement it for some reason or another, it's still obviously not as simple as a copy+paste operation.

Rei definitely managed to get a looksee around and see what makes SX tick: https://twitter.com/Reisyukaku/status/1016804828901756929

 

[Lacius]

Are these guys for real.... Come on guys, compile the cfw, build a bin for yourself and try it out. Its our very first CFW ^^ Happy days allright! Anyways, Rei allready stated a million times before, like so many others the cfw is a WIP, this means Work In Progress... (S)he is not done, he hasnt closed the software or anything (open source ftw) and sig patches are coming asap. Give it some time and i think we all will be running reinx in one way or another in about 2 months.

Again, great job on publising the code rei, we love it And dont bother about the flamers, a guy has to complain after all things said and done apparently

First, I agree with nearly everything you said, so don't get me wrong.

That being said, the signature patches are technically closed-source right now. You can read my earlier post on why I find that mildly disconcerting.

 

[Phenj]

What can you do with this CFW that you can't do with Hekate?

 

[kylum]

Since my sd card 128gb with all my saves on it i decided to just use a smaller 2gb formatted to fat32. now i get error "failed to initilize SD card" on booting. Have to hold down power 10sec to reboot. SD shows up just fine in OFW. GRR!!

 

[gothteen]

First, I agree with nearly everything you said, so don't get me wrong.

That being said, the signature patches are technically closed-source right now. You can read my earlier post on why I find that mildly disconcerting.

Ive read ur post and im not saying we dont 'have sig patches', we dont have them because there not in the main repo and closed source. Im not saying u cant do it, its just a bit of a sidetracking to get them to work. That said, its modulair, u can add almost anything i guess

 

[Lacius]

What can you do with this CFW that you can't do with Hekate?

For now, nothing. It opens the door to a functionally modular CFW, but modules don't exist yet. More importantly, signature patches will be implemented in the near-ish future.

Ive read ur post and im not saying we dont 'have sig patches', we dont have them because there not in the main repo and closed source. Im not saying u cant do it, its just a bit of a sidetracking to get them to work. That said, its modulair, u can add almost anything i guess

All of the work being done on signature patches is figuratively being done behind closed doors. While that's Reisyukaku's prerogative to do it like that, it makes the work on signature patches technically closed source for the time being.

Edit: That seems to contradict things previously stated about the needs and goals of ReiNX, though I explained above why I think it's being done this way.

 

[youngc29]

Your switch doesn't have the exfat Update then. Maybe that's the error, after booting.
Try formatting it to fat32

I will try that tomorrow then, curious though why does hekate (currently on the same exfat sd) boot up ok?

Seeing that someone else who is using a similar exfat sd card with hekate files on it but on 4.0.1 I am thinking it only works on fat32 and not because of the fw ver but could be wrong.
If a lower ver switch does not read exfat but only fat32 does hekate have something baked in to enable this?

 

[Darth Meteos]

All of the work being done on signature patches is figuratively being done behind closed doors. While that's Reisyukaku's prerogative to do it like that, it makes the work on signature patches technically closed source for the time being.

ask a question about the work and it will be answered
most of the answers are rei losing his mind over how damn frustrating it is to make this work
a couple of people got it to work, but they've gone awol so we don't know what the hell we're doing wrong
it's being a li'l shit right now, is what i'm saying