fatFS may be dependant on OS, but raw data, sectors, size and block diagram is carried by SD insfrastructure.. so it should work..Let's see, what happens to the peoples, which try to restore their NAND
I don't think gw team deal with AES so bad it doesn't decrypt the fw anymore isn't..(?)
well it worked out good for the DS and wii.....nintendo devices should just come with a hack buttonThey want to kill Sony finally with cheap hacking devices for their consoles
Well, the error is a blue screen of death... GOT TO BE MICROSOFT
im not sure i heard a few people say they never used emunand.....but at this point theres probably so much BS flying around its hard to know who is telling the truth and who is just making crap up......i say just go back to 2.0 if there is no games you want to play atm that require 3.0
well to be fair the clones are bricking peoples 3ds's by not knowing what they are doing and copying stuff they dont understand...its a bit harsh on the users, but its not exactly like gateway forced them to copy their launcher
so i'd go to 2.0...
anyway why are there blue screen errors, because first there were no errors (only gray lines) but the 3ds-corrupting errors
and back to 3.2 cuz 2.0 cant load the 3.2 sav files (corrupted save)
- Joined
- Oct 7, 2007
- Messages
- 4,426
- Trophies
- 3
- Age
- 36
- Location
- Levelland, Texas
- Website
- www.mariopc.co.nr
- XP
- 6,789
- Country
People need to start emailing Gateway demanding they stop bricking 3DS consoles for using modified launchers. I would understand if they wanted to brick the red gateway flashcart so it can't be used on modified launchers, but bricking a 3DS console is going too far. Nintendo has never intentionally bricked a console for having a modified firmware or flashcart, so customers should not have to expect that from Gateway. Plus Gateway never directly notified customers that they coded this in to happen. People should STOP buying the Gateway until they stop doing this. Vote with your wallet!
i dont think that is gateways fault,the problem may be by poor integration of the launcher of clone cards,and i dont think gateway has any way to stop that ,it is really rediciulus asking gateway to take care of firmware of clone cards ,to go further more the clone cards should have taken time to develop at least their firmware based on gateway data and not just cloning it over their hardware.dont blame gateway blame those that didnt code their launcher.dat
Gateway put a code in their launcher.dat which roughly works like this:
The random-number-generator uses the console date for initialization. That's why all the bricks occured after a certain date. The second part checks whether the launcher.dat file itself is legit. Any modification makes the checksum fail and therefore bricks the console.
Code:
if(<low 4bits u32 output from random-number-generator are zero> && <checksum over arm9 code is invalid>)
brick();The random-number-generator uses the console date for initialization. That's why all the bricks occured after a certain date. The second part checks whether the launcher.dat file itself is legit. Any modification makes the checksum fail and therefore bricks the console.
Similar threads
-
-
-
-
-
-
-
-
-
-
-
-
-
@
AncientBoi:
What Network is it on? I wanna see what you guys are talking about. N What time frame is it on? -
-
-
-
-
-
-
-
-
-
-
-
