D
Deleted-236924
Guest
I thought someone on this thread here linked to a forum post in a thread on the supercard forums about someone who got bricked?
I didnt see any, but I am just barely literate lol
--------------------- MERGED ---------------------------
Also, who is to say they wouldnt censor posts on the supercard forum. Just cuz I didnt see one when I was looking doesnt mean there isnt (wasnt) one there.
There really isn't a whole lot of difference between what CFW and Gateway can do right now. I would only recommend buying a Gateway if you have a New3DS, since rxTools still doesn't fully support it, and because when Gateway gets past the New3DS 9.6+ encryption, Gateway users will be the first to be able to get emuNAND updated on their systems.
On the topic of the brick code, I do think what Gateway is doing is a bit harsh, but ultimately the bricks are the fault of the DSTwo team for supplying software to their customers that they know have the potential to brick their consoles.
Please correct me if anything is wrong.
On the topic of the brick code, I do think what Gateway is doing is a bit harsh, but ultimately the bricks are the fault of the DSTwo team for supplying software to their customers that they know have the potential to brick their consoles.
Last edited by Karuta,
How are people retarded for not knowing? Obviously if they knew it was going to brick them they would not have bought the dstwo. Not everyone sits around reading every last piece of the forum. It is extremely unprofessional of gateway to brick users, end of story.
Last edited by funnystory,
gatecrap made the brickcode after DSTwo+ was released. So the bricks are at fault of gatecrap. Whenever gatecrap has communicate with SC about the brick is unknown. If they do then it gatecrap 75% to blame, 25% for SC, else it is 100% gatecrap to blame.
Agree. If you grandfather were going to buy a flashcart for your cousin, would he read all this gatecrap shit first before purchasing it??!??!? Or will he be already impressive by the demostration shown by a shop employee.
EDIT: Why i think gatecrap is to blame? Brickcode comes from them! They made it to brick player's console. There are enough other alternatives. Like reboot the console, or anything else that just not bricking player's console. This proves that gatecrap is build on money and not trust. One day they comes with new revision, they comes with new team name and new flash cart name. And they will brick all the flashcart they have sold so far. So we will buy the new flashcart from the new team. I think this might happen one day. For those close minded people go salute the shaddy practise of this team.
Last edited by Wekker,
http://forum.supercard.sc/thread-12523-1-1.html
so, if you brick your ***** by installing an uncompatiable firmware not made for your product, you blame the company who makes the firmware
funny the supercard team has nothing to say, they know they are guilty
so, if you brick your ***** by installing an uncompatiable firmware not made for your product, you blame the company who makes the firmware
Last edited by dsrules,
I have to correct that for a bit... formatting an EmuNAND should be possible without the GW software. Basically you'd just have to format your SD card to leave at least <size of NAND backup + 512 byte> free at the start. Partition Wizard should be able to do that. Then you use EmuNAND tool to inject a valid NAND backup - done. I'm actually thinking about including that option into Decrypt9, which would be the last nail in the coffin of GWs software for GW non-ownersWell then, you'd have to be using Gateway's stuff for that to be possible
I mean, you have to use Gateway's launcher to create emunand and stuff, but that's about it. Can even use an old version of their launcher that doesn't have brick code and instruct everyone to use that older version when setting up their CFW, and even if GW adds CFW detection code to their latest launchers, we don't care, we don't need their latest launcher anyway.
.
Well, I think we all knew this would happen
Who is to blame? Well, I would say mostly the user. When you violate your console's ToS, you must be aware that potentially anything you're doing can break it, and that, if it happens, you're the one to blame.
So, while we can say that Gateway's doing are wrong, can we really blame them? They are working on something that is, by nature, wrong, and the user chose to take the same path.
Who is to blame? Well, I would say mostly the user. When you violate your console's ToS, you must be aware that potentially anything you're doing can break it, and that, if it happens, you're the one to blame.
So, while we can say that Gateway's doing are wrong, can we really blame them? They are working on something that is, by nature, wrong, and the user chose to take the same path.
Last edited by Deleted member 370671,
SC team obviously knew about the brick code. There was a huge controversy about the bricks from the last incident, plus, on the download page for the new gateway firmware, they yet again warned the clone makers. Its not a matter of if gateway communicated with SC team or not, it was made obvious.
Last edited by Karuta,
What difference does it make whether or not SC knew or not. Gateway don't have to tell them a damn thing. It's down to Supercard to make sure what they release for their users is safe.
Better make that brick count 3. Gateway strikes again. Blah, I only tested it. It bricked my friends 2ds, but she has a NAND backup and hardmod. It was restored aprox. 50 minutes ago.
Thank goodness for those, i seriously need to get both of my 3DS XL's hard modded in case of a brick or accidental update
Gateway plugin with DS2+ card. It was a test to see what Gateway has to say about a clone card. I didn't believe it on the account of such a small brick count.
Do you think you can post how exactly the brick happened please? What kind of test were you performing? You plugged the supercard in once and it just died, that's it?
Thank you
If people are going to post that they have a brick it would be nice if you could just post all the information surrounding what the circumstances were in one place please and thank you.
Last edited by DayVeeBoi,
It wasn't necessarily me who actually ran the test. I had my friend do this test. She doesn't have an account here and I have no means to communicate with her atm.
So just for the record, you didn't have a bricked console? And you never saw a bricked console. And you don't know what happened to brick the console?
I didn't own the console, I did see the bricked console, I'm the one who restored it. It's just coincidental that she had left and I have no means of communication with her for the next 2 or 3 hours. I can maybe post pics later? Depends on her cooperation with me later. She's not my best friend and according to her, I'm kind of annoying.
i was originally thinking it would be ridiculously easy for gateway to detect DSTwo users, despite some people doing the old naive "well if it works on the official launcher.dat gateway will NEVER be able to block/detect it haha supercard pwns", straight away after release people noted that the DStwo always fails the SPI checks in diagnostics
#1 piss easy clone test for gateway to perform,
and seeing as the DSTWO+ has the DS and 3DS card in 1 they could also just scan the msd for the DSTWO kernel files and GW plugin.....now it they have opted to detect the DSTWO+ with either of these 2 methods it does leave room for legit users of gateway to end up bricked, say if someone uses the same microSD between a DSTWO+ and a legit gateway card or someone who has a gateway card that has a faulty SPI chip........maybe they use both and that would greatly reduce the likely hood of someone with a faulty gateway card + using the same mSD with a DSTWO
then again it could be something even more elaborate, challenge and response timing etc to differentiate gateway and dstwo users, would be good to find out the exact trigger though
#1 piss easy clone test for gateway to perform,
and seeing as the DSTWO+ has the DS and 3DS card in 1 they could also just scan the msd for the DSTWO kernel files and GW plugin.....now it they have opted to detect the DSTWO+ with either of these 2 methods it does leave room for legit users of gateway to end up bricked, say if someone uses the same microSD between a DSTWO+ and a legit gateway card or someone who has a gateway card that has a faulty SPI chip........maybe they use both and that would greatly reduce the likely hood of someone with a faulty gateway card + using the same mSD with a DSTWO
then again it could be something even more elaborate, challenge and response timing etc to differentiate gateway and dstwo users, would be good to find out the exact trigger though
Similar threads
-
- Portal
- No one is chatting at the moment.
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
-
-
-
