It could make sense that the problem is related to the region free patch, since the bricks started after a couple of days it was released, but who knows; I myself never tried that patch since I don't know games from another region.
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.
Look, you are right in the part that they should have warned that the launcher had save issues, but it seems that they focused a lot on the emuNAND for that release (beta release), and now you and everyone must know why that feature needed a focus of attention.gateway quote: We pride ourselves to do thorough testing before release, the same cannot be said for our so-called “competitors
gateway quote: We pride ourselves to do thorough testing before release, the same cannot be said for our so-called “competitors
GUARANTEE that the Gateway is not affected, even though there were reports from supposed Gateway users..
Take note that the Gateway News Update attributed the bricks to 'flawed copying or modifying'. It is clear that there are far more brick reports from r4i deluxe gold and 3dslink users and most if these can probably be attributed to the modified launchers. Just because you are a Gateway user though does not mean you are 100% immune.
There is always the possibility that something went wrong when you copied the launcher to the sd card. With all these cheap knock-off sd cards and sd readers going around, I would certainly not write-off the possibility. To be safe I would recommend doing a checksum test on the launcher.dat.
It is possible that data corruption can even occur during decompression if there is some sort of fault in your computer's memory or hard drive. So if you are paranoid or don't completely trust your hardware, redownloading and decompressing another copy to do multiple checksum tests certainly would not hurt.
If you don't require EmuNand, revering back to Gateway 1.2 is probably the safest course of action though.
Those reports on these boards are related specifically to using "data management" features, not to the launchers.
They are two different problems.
The R4i bricking happens by just using the launcher.
The Gateway bricking happened due to problems of "data management" and emuNAND/sysNAND. Which makes sense. Don't fiddle around with data management if you are on emuNAND.
There is 1 gw user bricking console by using the "data management", that is the same person who started the bricking thread on this forum. And there is atleast, as far as I know, 1 gw user just using the launcher and bricked his console.(Posting on official gw forum) 3 other gw user reports are on a spanish forum which the causes are unknown to me. So no, gw bricking isnt only related to data management option.
There's a reason it was a beta release ;P
There is 1 gw user bricking console by using the "data management", that is the same person who started the bricking thread on this forum. And there is atleast, as far as I know, 1 gw user just using the launcher and bricked his console.(Posting on official gw forum) 3 other gw user reports are on a spanish forum which the causes are unknown to me. So no, gw bricking isnt only related to data management option.
Do you have the link of those reports in spanish? I would like to read them. I have visited the forum, but all the info there is scattered and I didn't find anything relevant three days ago.
It's all pretty much compiled here:
http://www.elotrolado.net/hilo_ho-bricks-en-3ds-error-bootrom-8046_1972148
Do you have the link of those reports in spanish? I would like to read them. I have visited the forum, but all the info there is scattered and I didn't find anything relevant three days ago.
It's starting to look that way to me too.Is it not strange, all bricks happened at the same day?
I'm 100% sure they included time related bricking code. And as we know, their hardware diagnostics are not very reliable, the clone detection maybe fails too --> brick, even with the original GW