Hacking Discussion Consoles brick, learn how to handle it!

[SaffronXL]

Hell I should have checked the src myself, but it was me being lazy...

And that, in summation, is the whole situation folks.

YOU are the one making the accusations, and yet you have PRESENTED NO EVIDENCE WHATSOEVER, EVEN THOUGH YOU'RE THE ONLY ONE WHO CAN.

 

[JellyPerson]

hey everyone, chill. it was probably a hardware error. besides, if you have a nand backup, just reflash it.

 

[M7L7NK7]

hey everyone, chill. it was probably a hardware error. besides, if you have a nand backup, just reflash it.

Did you even read the thread? They did flash the NAND

 

[linuxares]

Okey, I just gonna let out a warning right away. If this turns bickering. We will lock it without hesitation. We're pretty fedup with reports about bickering lately, and if this is turning south. We will end it.

Also, Evilsperm, if it's the real person. Have years of experience with hardware and software development. Either it's a hardware problem that happend to exact same time, or it's a bug in the CFW somewhere. Each source should check if they can find the issue so it never happens again.

 

[JellyPerson]

Did you even read the thread? They did flash the NAND

:thinking: huh, well like i said, it must've been a hardware error

 

[linuxares]

:thinking: huh, well like i said, it must've been a hardware error

Remember, the Switch is so fragile you can toast the LCD in the Switch with software modifications. This is why it's so important for the CFW devs to know what they're doing.

 

[JellyPerson]

Remember, the Switch is so fragile you can toast the LCD in the Switch with software modifications. This is why it's so important for the CFW devs to know what they're doing.

right. however wasn't raj's cfw like a compilation of other tools that were already released?

 

[SaffronXL]

Also, Evilsperm, if it's the real person. Have years of experience with hardware and software development.

I would expect someone with so much experience and respect in the community to put forth some evidence behind their accusations, wouldn't you? Either this isn't the real ES, or that respect is greatly misplaced.

 

[linuxares]

I would expect someone with so much experience and respect in the community to put forth some evidence behind their accusations, wouldn't you? Either this isn't the real ES, or that respect is greatly misplaced.

It's hard to find the evidence if the Switch is fried. Also I'm pretty satisfied with the explanation he been doing, as I said. If it's the real person.
This is why I hope the parties try to find out where the problem is, or if it's just a wave of unluck.

 

[Meepers55]

I really don't think you "get" it.
Lets say the official dock toasted the charge controller the nand would still be intact!
The console would still boot from RCM mode its as simple as that. In this case it does not what so ever.
The dock bricks don't exhibit behavior like this, and of coarse if I want to swap out the charge controller to do further testing I can, but I wont because its not even worth my time. As soon as that symptom is fixed I will still need to deal with the nand issue being totally muffed.
The system will not boot OFW or CFW even after a reflash of the original nand.
I really don't care if gbatemp kids don't want to do their homework and take my warning, go ahead and brick your system...
I just hope you have deep pockets though for a new one
My console could have been a perfect storm for something to go wrong, but do you really want to zap yours to find out?
I have hundreds of hours on this system with and without our mod in there, including a trinket as well during early development.
There have been no instances of anything going wrong until now with rajnx.
Hell I should have checked the src myself, but it was me being lazy...
Guess I'll have to look into it further when I have the time but as for now I'm putting all my $ on an issue with the cfw.

Also I was in no way attacking raj, and the tolls that do are assholes.
Like I said he puts out good work, this could have just been a fluke but its better to be safe than sorry!
This same exact ting happened in the ps3 scene and it bricked thousands of consoles before anyone knew what hit them.

If you have enough free time to type long replies with barely any substance then I'm sure you have the time to do some tests. If you get to the bottom of this you can prevent many more bricks and you'll be remembered as that one guy with the modchip company who prevented Switch bricks. Sounds good for sales.

 

[rajkosto]

seems that there's some confusion here, as evilsperm thought that you could run Horizon normally on a dock-bricked switch if you use RCM/a CFW (thus the "it broke the nand" claims). This is not true, it will freeze on the Nintendo Switch logo (exactly the symptom he has) if the PD chip is broken. See here: https://www.reddit.com/r/NintendoSw...d_my_third_party_dockbricked_nintendo_switch/
It's likely replacing the M92T36 chip will fix his Switch, I hope he tries it.

 

[SaffronXL]

. Also I'm pretty satisfied with the explanation he been doing, as I said. If it's the real person.

I'm not at all satisfied with his explanation. If he's making and selling a product that will be used by other people, he should know exactly why his own Switch busted. If not, how will he help his customers when the same thing happens to them using another CFW? Beyond unprofessional.

I otherwise agree with you 100%.

 

[evilsperm]

I would expect someone with so much experience and respect in the community to put forth some evidence behind their accusations, wouldn't you? Either this isn't the real ES, or that respect is greatly misplaced.

You want me to bring you bulletproof evidence?
Good luck with that...
Maybe if I had a camera capturing everything I do 24/7 you might be in luck
I'll order the M92T36 and swap it out as raj asked, because either way its dead.
Like I said it could have just been a perfect storm, but its better to be safe than sorry don't you think?
But if you like by all means please keep running the fw and use an official dock, report back in a week if your system is still alive

 

[rajkosto]

But if you like by all means please keep running the fw and use an official dock, report back in a week if your system is still alive

Don't just run that CFW. Run any possible CFW and stock, in all possible configurations (docked/undocked/firmware versions). The bigger the sample size, the better. 1 is not a very reliable sample size.

 

[Serfrost]

... thought that you could run Horizon normally on a dock-bricked switch if you use RCM/a CFW. It will freeze on the Nintendo Switch logo (exactly the symptom he has) if the PD chip is broken. See here: https://www.reddit.com/r/NintendoSw...d_my_third_party_dockbricked_nintendo_switch/

It's likely replacing the M92T36 chip will fix his Switch, I hope he tries it.

I'll order the M92T36 and swap it out as raj asked, because either way its dead.

But if you like by all means please keep running the fw and use an official dock, report back in a week if your system is still alive

It'd be nice to know if the M92T36 does fix it for you. If that's the case.

On the other hand, I'll keep running RajNX. I trust his work. If something goes south without me touching anything henceforth, then I'll question. But otherwise (so far,) nothing has went wrong and it's been a day or two with me both running games and also installing them.

The one fault I did have during my Switch setup was before I ever used RajNX, and it was my own fault. Raj helped me out of that, so all's well on my end.

 

[evilsperm]

Don't just run that CFW. Run any possible CFW and stock, in all possible configurations (docked/undocked/firmware versions). The bigger the sample size, the better. 1 is not a very reliable sample size.

I agree, I didn't mean to come off as a dick as well, I just don't want to see people brick consoles that they can't afford to replace

 

[TheZander]

I agree, I didn't mean to come off as a dick as well, I just don't want to see people brick consoles that they can't afford to replace

Can you temporarily swap batteries with a charged console and then flash your backup? Would the dead battery charge if put in another console?

 

[mooglazer]

I've said it before, and I'll say it again.

I would strongly advise anyone who is a novice ... to simply build themselves a trinket+cell battery rig:
https://www.reddit.com/r/SwitchHaxing/comments/8vze4a/tiny_trinket_m0_and_coin_cell_battery_dongle/
Opening up a $300 USD console without proper experience, skills and tools is just plain idiotic.

That said, IMHO whatever happened to the "bricked" switch is likely not due to RajNX.

All of the major software bundles -- RajNX, ReiNX, TumGER, etc are all effectively the same source code base. Even SX OS is based on the same code. I know a lot of you probably don't want to hear that, but that's the fact of the matter. Calling it a "CFW" or a "starter pack" doesn't change the fact that everyone is repackaging Atmosphere, Hekate and Tinfoil. There is no "CFW war" -- and I think it's entirely imbecilic that a bunch of trolls are allowed to show up and harass anyone who might even consider improving the scene. It's no damn wonder most of the talented developers have left.

What is troubling to me is the fact that someone who is selling a product has the audacity to show up and blame their own hardware failure on someone else first rather than debugging properly and assuming the issue is not with their own install and/or hardware design. There are several variations of the same trinket m0 (Atmel ATSAMD21) design, and yes, they are all literally the same design, with minor modifications. This particular hardware design is untested, and has had no real reviews or hardware samples that I'm aware of -- there is no other test case to verify that it isn't user error. If you buy from someone, and they react this way when they discover a bug in their own product, how do you think they'll behave when their product bricks your switch? Is this something you want to put your money behind?

I personally run an internal install trinket m0 (bought from adafruit) with RajNX and it runs beautifully.

We are all on the bleeding edge here. If you don't have a Switch to throw away, then STAY FAR FAR AWAY. If you get banned, you cook your switch, etc etc -- YOU are responsible. It's all on you.

No offense intended to anyone, I just believe the nonsense has gone far enough.

 

[OrGoN3]

I agree, I didn't mean to come off as a dick as well, I just don't want to see people brick consoles that they can't afford to replace

And people shouldn't be modding if they can't afford to replace it. It seems people still think, even software modifications, are always safe to use. Sigh.

 

[SaffronXL]

And people shouldn't be modding if they can't afford to replace it. It seems people still think, even software modifications, are always safe to use. Sigh.

No man. This shouldn't happen. We shouldn't waste this opportunity to learn and possibly prevent it from happening to someone else. But I think what's important to remember is the Switch in question had hardware modifications. Whether the issue stemmed from the hardware or software end, there is valuable information to be obtained.