Seems they found the problem with the bricked devices. Modified launchers could be the problem, but then again, it could just be a way for GW to push their cart vs. clones. Either way, team statement is below.
There seems to be a lot of confusion about all this bricking business. I'll just leave my machine off till the dust settles.
So, this bluescreen bootrom error, causes bricking? Well, I'm not changing launchers for the region free patch anytime soon it seems...
If anything Gateway shouldn't proud themselves of, is that they are testing thoroughly before release. I never experienced any problems with Gateway untill 2.01a with the emu feature. That release made me experience save errors and save blocks when exiting games through the home menu. I understand that the EMU NAND thing was for beta testing. But the save feature was working fine for me. Come 2.01a, the save feature was bugged.
Now F off Gateway. I loved you for what you initially did. Payed a fortune for your card. And then you make updates to mess things up.
Now F off Gateway. I loved you for what you initially did. Payed a fortune for your card. And then you make updates to mess things up.
There's a reason it was a beta release ;P
That is exactly my point, and the save feature didn't ned a beta. See, the save feature worked all along from the start, you know - from the get go. They release something, and they messed things that worked up.
Why not just let us test EMU NAND instead of the whole deal. And if anything, they should know all by themselves that the save feature was bad. There has been so many posts about it.
At least they could warn us.
A few weeks ago, I wrote this:
I want to add my view on this beta.
Unlike the beta for region spoof, which was for a closed audience, this beta is an open beta. But the problem with this beta is, that users are at a HIGH RISK of rendering their 3ds on 4.x completly useless.
I dont for one single second buy the argument that GW fans would be mad if they had to wait another week for a fully fledged working release. Because what Gateway risk by this manouvre is losing customers, since an updated 3ds isnt able to run GW.
I don't consider myself as a "dumb as a space shuttle" to this hacking thing, but i sure hesitated when i saw that this was a beta, where people with not so much knowledge with, copying their NAND. I myself waited 24 hours before doing it, so I could see the inial problems and fails from users.
Now here we are a few days later, the result is as expected. A few people actually did update their sysNAND. The instructions for copying and formatting the NAND are terrible at best. I had to redo the whole thing several times over and over again, because i were never sure wtf the instruction really wanted me to do. The instructions has to fool proof.
A certain "special" feature this release has (and devastating too) , is that when you go into system settings to verify that you are on gw3ds firmware and exit systems and settings for the first time, its hard to tell what NAND you are on, because you havent made any significant differences. Alas, people are back on their sysNAND and they start updating.
That small thing should be highlighted with big fcking flash text in the instructions.
If anything, this beta should be kept closed like a nun's ****, whereas spoofing could easily be open.
I did manage to update it correct, but my heart skipped 2 beats when i took the chance updating. And i am right now enjoying the new zelda.
I would like the GW crew to be more elaborate when do their instrutions, and really reconsider when a beta is suitible for open tests
For those of you that did screw up in this beta, I fully understand why you messed up and I feel sorrow for you.
And i still stand by that post 100 %
- Joined
- Sep 8, 2009
- Messages
- 8,079
- Trophies
- 2
- Location
- One's inner self
- Website
- 3dsdb.com
- XP
- 2,440
- Country
lol well it doesnt
becuase its using Gateways own stuff
R4i moddify alot more to there own
rarther than just moving gateway code from one part to another
Normmatt is maybe one of the best coder/hackers the DS/3DS scene has. its more likely its the clones and not Normmatt work.
So, you partake in a beta firmware and complain about the very things Gateway warned could happen. Would you be one of those first in line to complain about how a firmware release is taking forever or is underfeatured and then explicitly say, "They could at least give us a Beta firmware!!!!"
Yeah, I bet you would.
Oh you have proof? i would consider contacting gateway then... maybe they will remove that warning.
Exactly, the most reliable source right now is the gateway team.
If the team he based his work off of warns people not to use it, like I said.
that`s good enough for me.
No one knows yet, but there are reports on the official gateway forum of random bricks using only gateways launcher.dat
as I said in a previous post:
I seriously thought that image was your signature, until I logged in because I wanted to tell you that you didn't put anything after "..as I said in a previous post:". As for what's causing all of these bricks to happen seemingly at around the same time? It seems a little suspicious.No one knows yet, but there are reports on the official gateway forum of random bricks using only gateways launcher.dat
as I said in a previous post:
Ok, I'll stop soon, as it seems I am whining. But before I stop here, do me this favour: Copy/paste where in the release notes of 2.01b they warned us that saves would risk being corrupted.
I take it as though people are using gateways launcher file with clone cards and clones launchers with gateway card causing the issue and anyone modding the launcher file. I don't see gateways launcher file causing the bsod I think its people playing with files that they shouldn't be and of course no one will admit it.
Well, obviously if they knew that the save files were at risk they wouldnt had released it; it is a beta release, bugs are typically expected. If what you want is an almost bugfree software you shouldn't had download a beta release.
Similar threads
