Hacking GW Team warns against modified launchers

  • Thread starter Thread starter sonic2756
  • Start date Start date
  • Views Views 44,533
  • Replies Replies 239
  • Likes Likes 2
Let's see, what happens to the peoples, which try to restore their NAND :rofl:
fatFS may be dependant on OS, but raw data, sectors, size and block diagram is carried by SD insfrastructure.. so it should work..

I don't think gw team deal with AES so bad it doesn't decrypt the fw anymore isn't..(?)
 
If gateway was behind the r4i....why bother making a shady blatant copy of the gateway firmware.....they would have everything required to just edit the pictures and logo's and recompile it into a different looking firmware, also why would they then go and point the finger at themselves....they could of just as easily blamed it on Nintendo or something if r4i was their own creation. Truth is it's as gateway have always said they are their innovators and the clones are the imitators
It's all part of their secret business plan :ninja:
 
ohhh i see...and i know who is behind it all.........NINTENDO....why else would there be a bug in the FW for gateway to use....its the only way!

Nintendo=Gateway=R4i=Smealum=...Microsoft?
 
  • Like
Reactions: cearp
ohhh i see...and i know who is behind it all.........NINTENDO....why else would there be a bug in the FW for gateway to use....its the only way!

Nintendo=Gateway=R4i=Smealum=...Microsoft?
Well, the error is a blue screen of death... GOT TO BE MICROSOFT
 
  • Like
Reactions: gamesquest1
so the bleu screen error only occurs in emunand? and till now my r4i worked fine (3.2)

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
 
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


does bravely default require 3.0?

yellows8 checked it. Gateway is intentionally bricking consoles, which are using clone carts.

wut WHAT?
 
yellows8 checked it. Gateway is intentionally bricking consoles, which are using clone carts.

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
 
Nope. It only needs firmware spoofing wich comes with the 2.0 release.


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)
 
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!
 
  • Like
Reactions: mr. fancypants
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
 
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!

pretty sure it's people NOT buying Gateway that causes this problem for them in the first place
 
Gateway put a code in their launcher.dat which roughly works like this:

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.
 

Site & Scene News

Popular threads in this forum