Hacking So, no bricks reported yet for Gateway 2.1 Ω?

  • Thread starter Thread starter CraddaPoosta
  • Start date Start date
  • Views Views 8,671
  • Replies Replies 63

CraddaPoosta

Sepatown, my damie.
Member
Joined
May 3, 2010
Messages
1,325
Reaction score
994
Trophies
1
XP
2,782
Country
United States
Since I have neither the tools nor the expertise to actually check the newest firmware, have there been any reliably-confirmed bricks by users of Gateway 2.1 Ω?

Especially directed to those with a hardware SD mod (ahem, gamesquest1, harumph).

Just wondering if we could finally put the bricking debacle behind us.
 
I know that you were able to cause a brick on your unit with an alarming degree of reliability, running the diagnostics test, gamesquest1. So, have you had time to see what happens if you try booting into it repeatedly on Ω?

You're pretty much the go-to guy for defending this community from bricks. This post was essentially for an audience of one.
 
yeah i tried it a whole bunch of times before it got leaked, but it was leaked faster than you could say boo, but anyways heres the comment i was talking about
lol wrong one...ill try find it XD
 
some dev's have looked into the code and it seems its actually gone :)
Any solid quotes I could use or is the matter hush-hush? I'll understand if it is and I won't include the nicks in the post, but I'd still like to know if they were reputable sources. I like consistency and I value user safety, I wouldn't want to write something that isn't true and sign it with my name. :) Please contact me via PM if possible.
 
Mathieulh said he didn't find it, but it doesn't mean it's not present (or another form of it).
He also said they improved their obfuscation, so who knows...

edit: :ninja:'d
 
yeah, i know, but so far it seems is he right, there was also another dev looked into it using the word "we are looking into it" so im sure there is a few dev looking into it so if they would of found something even slightly suspicious they would of came and announced it.

with the stance of the devs with flash card manufacturers I'm not too certain they would ever some out and say "yeah its safe"...just because they wouldn't want to help them out, but they would certainly announce otherwise
 
That's really why I was asking whether or not anyone with a hardware mod had actually TRIED to brick their console, the same way gamesquest1 did when he pinned down diagnostics mode as being one of the triggers of the brick in the first place. Whatever we discover about the actual code, it would still be useful to see if someone had actually tried to replicate the bug/brick with the most recent firmware. I would totally do it if I had the hardware available to me.
 
The brick code may still be present, but it seems to have been improved.

The devs from Project Pokemon said that the brick code was still there... in 1 April.
 
The brick code may still be present, but it seems to have been improved.

The devs from Project Pokemon said that the brick code was still there... in 1 April.

It wasn't an april fools joke.

said post showing the bricking reference

There's still bricking code and all of their obfuscation tricks, however it's likely that they removed the post-diagnostic crc brick (their fault) and shifted it elsewhere.
 
I've tried everything to brick my 3DS (have a hardware mod and RPi). The last one to check is to see if it bricks when it runs out of battery while in emuNAND.
 
  • Like
Reactions: CraddaPoosta
well nothing short of editing the payload it would seem, just been running a bunch of times with the file edited by one byte to mess the checksum of the launcher up...still no brick that way
 
  • Like
Reactions: CraddaPoosta

Site & Scene News

Popular threads in this forum