Hacking [No longer maintained] RajNX - starter pack for Nintendo Switch

[uberNeko]

Hi

 

[Kioku]

I'm gonna play devil's advocate here.. but a hardware fault is entirely plausible...

 

[Darth Meteos]

<Bullshit filter activated> Scratch this one off as an all time new low for the weeb minion shit team.. seriously its always the same low life's spreading negative propaganda based off of one idiots claim to jump to conclusions without substantial proof.

You seriously have got to be a Raj-alt. All you ever do is spout bullshit lines, even when something terrible happens.

@rajkosto I thought you people were better than this, but you don't even care that you're breaking peoples' hardware. I thought that, even though we're having a petty li'l fight here, we could still prioritize the experience of the end-user, but here you are, shouting fake news instead of fixing the problem because it's more convenient to you. You are the lowest scum. Mods, lock this thread when?

 

[rajkosto]

We all know if it was ReiNX that caused a brick you would be crowing about it. You are a hypocrite. Its not a game, its not a joke. Wise Up.

The replaced loader and sm sysmodules do not interact with hardware. The only thing that could possibly even start to misconfigure hardware is the bootloader, which is why for these first versions i've based it off the tried and true hekate that everyone's been using for a long time now (you can audit my changes vs stock hekate to see that there's no hardware initialization code changed).
So the brick couldn't have possibly been caused by it, since he was running tomGER sdfiles pack before (which uses stock hekate) and was apparently fine.
More than likely this is a coincidence caused by some hardware fault (or would you be saying that all these hardware faults are caused by CFW too ? )

 

[efxonly123]

Yup, a battery issue while docked. Sure.

How did nintendo brick all of the switches with 3rd party docks???

 

[Reisyukaku]

I'm gonna play devil's advocate here.. but a hardware fault is entirely plausible...

im gonna play double devils advocate and say that the context this code runs in allows you to easily fry hardware. Although RajNX is just the product of salt. A simple hekate fork and a 'meteos-esque' pack.. so really make me think.

 

[palantine]

The replaced loader and sm sysmodules do not interact with hardware. The only thing that could possibly even start to misconfigure hardware is the bootloader, which is why for these first versions i've based it off the tried and true hekate that everyone's been using for a long time now (you can audit my changes vs stock hekate to see that there's no hardware initialization code changed).
So the brick couldn't have possibly been caused by it, since he was running tomGER sdfiles pack before (which uses stock hekate) and was apparently fine.
More than likely this is a coincidence caused by some hardware fault (or would you be saying that all these hardware faults are caused by CFW too ? )

If the situation was reversed would you be defending ReiNX and asking others to wait and see? Would you be urging caution and to let cooler heads prevail? Or would you be the one saying "I told you so, those guys are incompetent code stealers".

Your previous actions speak more loudly than your words ever could on this.

 

[SaffronXL]

I will tell you all point blank its rajnx fw, use this and expect a FULL brick that cant be recovered PERIOD!

Correlation != causation

Why fix your own work, when you can blame someone else's instead, huh?

 

[ExploitJunkie]

If I had minions, they'd be doing my job for me, so I wouldn't be so overstressed all the time.

That being jumping to conclusions and spreading negative propaganda based off one users claim?Take a break your jobs done.

 

[Kioku]

im gonna play double devils advocate and say that the context this code runs in allows you to easily fry hardware. Although RajNX is just the product of salt. A simple hekate fork and a 'meteos-esque' pack.. so really make me think.

Don't misunderstand, I'm not swinging for the opposing team here. I don't know the technical details of the code.. so, I can't argue for (or against) what it is.

 

[Reisyukaku]

Don't misunderstand, I'm not swinging for the opposing team here. I don't know the technical details of the code.. so, I can't argue for (or against) what it is.

Nah you're fine. just pointing out theres an argument for both software and hardware points of view.. but when that rajnx first thread came out it was a payload with no source.. So its reasonable people are skeptical.

 

[Darth Meteos]

That being jumping to conclusions and spreading negative propaganda based off one users claim?Take a break your jobs done.

Spreading? I'm talking about an issue in the relevant thread! What if you're wrong? I had a similar issue a week ago with Tinfoil locking consoles, and I had to motor to solve that problem. Where's your motor? Oh right, it's too busy going "fakenewsreinxistrashfakenewsreiswitchedisacult"

 

[evilsperm]

Coming from myself as a hardware and software engineer, this want a hardware fault of SwitchME, and it sure as hell didnt drain the battery when its sitting at 100% right now as it was at 100% when it popped so you can forget that it had anything to do with the SwitchME or you might as well say its all trinket installs as well and there hasnt been 1 post anywhere about this issue happening. Lets take a step back FORGET the fact the battery is totally FUCT along with the charge controller. The console powers on while docked! It powers on when plugged in with usb to pc.
...so do tell me how the internal chip is stopping it from booting...
Because I have even removed the chip and put it in another switch I have here and hey guess what? Boots just fine
Also with the chip removed from this bricked console, still boots rcm just fine...
So you can talk out your ass all you like that this was a hardware issue but clearly it isnt as it can still boot fusee without issue without or without SwithME
What this console sure as fuck cant do is boot any OS what so ever even after full nand restore, so please with all your wisdom in creating custom firmwares for over a decade tell me what you think is wrong...
Because I've seen first hand cfw shit brick a system to the point of no repair, not only from winibricko but when we created the very first working of rebug on our dex systems we fucked around with syscon and made our console $2000 paperweights!
So don't go telling me a cfw cant fuck a system to the point of no repair.
If I though for one second it was hardware related I wouldn't have said a word and just tossed this one in the trash.

 

[Centergaming]

fuckin christ man.. can someone lock this thread?

 

[rajkosto]

Leftover flux around the memory area/inductors (even without running CFW) from modchip installation can do this: https://media.discordapp.net/attach...39/471035447993303040/IMG_20180723_202612.jpg

 

[M7L7NK7]

This scene is fucking toxic and I'd hate to be a developer

 

[Kioku]

This scene is fucking toxic and I'd hate to be a developer

You say that, but devs are more than half the drama here..

 

[ExploitJunkie]

What if

this lol

Spreading? I'm talking about an issue in the relevant thread! What if you're wrong? I had a similar issue a week ago with Tinfoil locking consoles, and I had to motor to solve that problem. Where's your motor? Oh right, it's too busy going "fakenewsreinxistrashfakenewsreiswitchedisacult"

You claim to be this community mediator but I don't buy it at all. You come off as flaky in that regard and all it does is make bad reflections for ReiNX overall in general.

 

[M7L7NK7]

You say that, but devs are more than half the drama here..

Good point

I mean the ones who really are innocent and get attacked

 

[rich6619]

<Bullshit filter activated> Scratch this one off as an all time new low for the weeb minion shit team.. seriously its always the same low life's spreading negative propaganda based off of one idiots claim to jump to conclusions without substantial proof.

I agree. This is beginning to get a bit ridiculous now...almost childish.