Hacking Gateway update regarding rumors

  • Thread starter Thread starter gamesquest1
  • Start date Start date
  • Views Views 79,122
  • Replies Replies 472
  • Likes Likes 7
Has nobody with a bricked 3DS tried to flash the NAND and see if it is fixed or not? At least I myself haven't read any report about this.
 
Has nobody with a bricked 3DS tried to flash the NAND and see if it is fixed or not? At least I myself haven't read any report about this.

They've been saying it changes the NAND size to think it has 0 bytes of space and won't allow anything to be flashed to it.
 
Has nobody with a bricked 3DS tried to flash the NAND and see if it is fixed or not? At least I myself haven't read any report about this.

Apparently it does not fix it. I can't find a specific post for you, but it also sets the emmc controller to 0 bytes, so can't reflash as it thinks there is no room.

Ninja'd :ninja:
 
  • Like
Reactions: inuyasha555
Not sure if anyone has posted anything like this yet because there is so much speculation, but i wanted to post my findings. Im running an R4, no problems to report, I'm on the R4 3.2FW.
SHA: 74d3e2cfab7bb72abc6d1bc9c3fcfae6165ef19d
MD5 : 4c56b98e1cd1f06a270d97641be571f1

Again, no problems, just booted it up normally, I also matched the SHA/MD5 with the downloaded file from the rids.cn website and can confirm they are the same. Not sure if this helps, just wanted to add my 2 cents :)
 
They've been saying it changes the NAND size to think it has 0 bytes of space and won't allow anything to be flashed to it.

Apparently it does not fix it. I can't find a specific post for you, but it also sets the emmc controller to 0 bytes, so can't reflash as it thinks there is no room.

Ninja'd :ninja:

Who said this? The "trusted developers" or actual clone users? Because I also read the thread.

Not sure if anyone has posted anything like this yet because there is so much speculation, but i wanted to post my findings. Im running an R4, no problems to report, I'm on the R4 3.2FW.
SHA: 74d3e2cfab7bb72abc6d1bc9c3fcfae6165ef19d
MD5 : 4c56b98e1cd1f06a270d97641be571f1

Again, no problems, just booted it up normally, I also matched the SHA/MD5 with the downloaded file from the rids.cn website and can confirm they are the same. Not sure if this helps, just wanted to add my 2 cents :)

lol that's not how it works.
 
Who said this? The "trusted developers" or actual clone users? Because I also read the thread.



lol that's not how it works.

How does it work , i would like to know....dont want to brick my unit.....so the SHA/MD5 doesn't matter?
 
How does it work , i would like to know....dont want to brick my unit.....so the SHA/MD5 doesn't matter?

Nope, it doesn't matter if you are not using Gateway, so by using the R4i launcher (which is a modified Gateway launcher) you are risking your 3DS.
 
tbh i heared that the card reader need to be very specific to allow the reading and writing of the nand, it may just be the case that the first person who tried had a incompatible card reader......i would imagine rewriting the emmc controller board would be pretty complex from within the 3DS...at least more complex than it would be worth to prove a point.........one final note people keep over looking is this post from gateway


23/12/2013
First of all, thanks to everyone who has been testing our public beta.

We mentioned previously that we would have a solution against accidental updates, but we decided not to release this just yet.
While we did succeed in preventing accidental updates for our test 3DS unit, it took trial and error to get it in that state, and we bricked the unit many times before succeeding.
Ultimately we decided that it was too dangerous for public use right now.

surely this "evil" code that was found could be beta features that are not actually used in the firmware but are a way of preventing the sysnand from being wrote to thus preventing accidental updates and bricks........this would tie in with the previous post made by gateway about developing a way to stop nand writing when in GW mode, and also tie in with the fact they said it was buggy and caused bricks...thus it was not included

its also completely feasible that randomly modding a firmware you dont really understand you may inadvertently activate stuff that has been specifically disabled for a reason
 
Nope, it doesn't matter if you are not using Gateway, so by using the R4i launcher (which is a modified Gateway launcher) you are risking your 3DS.

Since the SHA/MD5 doesn't matter, can GBATemp remove it from the homepage, or does it "only" matter for Gateway users?

Thanks for the quick reply....
 
Credier

http://gbatemp.net/threads/warning-gateway-team-bricks-card-on-purpose.360568/

"When the brick code triggers it bricks the firmware and reprograms the eMMC NAND to have a size of 0 bytes."

Thank you, but I'm taking this as speculation since it doesn't come from a user with a bricked 3DS. Sadly, the guys who were trying to flash their NAND haven't reported their progress as up today.

Since the SHA/MD5 doesn't matter, can GBATemp remove it from the homepage, or does it "only" matter for Gateway users?

Thanks for the quick reply....

This only applies to the original/unmodified Gateway launcher, also that info is outdated and even if the launcher is corrupted, it will be safe, but again, only if it's the original launcher.
 
Thank you, but I'm taking this as speculation since it doesn't come from a user with a bricked 3DS. Sadly, the guys who were trying to flash their NAND haven't reported their progress as up today.



This only applies to the original/unmodified Gateway launcher, also that info is outdated and even if the launcher is corrupted, it will be safe, but again, only if it's the original launcher.

Well fine then I'll remove it! :angry: :cry:
 
  • Like
Reactions: kyogre123
It is supposedly confirmed it wont flash back by multiple non english speakers, which we get as semi broken translations. but also a guy here said he bought a 3DS XL and R4i, bricked it, returned to shop he purchased from, and guy flashed his nand back fine, and i doubt GW will trigger bricks ever, i have had sd corruption and no brick, just got message from ds, it was unreadable and needed formatting, swapping to an alt, 3DS worked as normal, if you are using their unmodified launchers, corrupt or not, YOU WILL NOT BRICK
 
OK. Well if you mean different and not shocking, then just say different? I just thought shocking makes the article sound more like anti-Gateway opinion than impartial news. Anyway.. peace and love to all!
 
It is supposedly confirmed it wont flash back by multiple non english speakers, which we get as semi broken translations. but also a guy here said he bought a 3DS XL and R4i, bricked it, returned to shop he purchased from, and guy flashed his nand back fine, and i doubt GW will trigger bricks ever, i have had sd corruption and no brick, just got message from ds, it was unreadable and needed formatting, swapping to an alt, 3DS worked as normal, if you are using their unmodified launchers, corrupt or not, YOU WILL NOT BRICK


I sit in on IRC too much for my own good and heard similar if not exactly the same things. From what I heard, this issue triggers from exiting System Settings in EmuNAND, and then becomes irreparable as the real NAND is zeroed out. Can't reflash either.

EDIT: I'll change the word to concerning if it makes you guys happier. *mumbles something about people being picky about words....*
 
OK. Well if you mean different and not shocking, then just say different? I just thought shocking makes the article sound more like anti-Gateway opinion than impartial news. Anyway.. peace and love to all!

I thought the article made Gateway sound like they had a giant stick up their ass. I mean, I like Gateway and all they've done, but they always respond to questions and problems with "Gateway Master-Race, if you don't follow only us, you're fucked".
 
Yup, seems multiple people have said the NAND being zeroed, making your NAND backup pointless, while only 1 has said it was fixed, and it always seems to be todo with system settings, with people blaming it on changing stuff in the settings, when in fact its when it exits the EmuNAND settings and falls back to a blank RealNAND
 
Gateway put protection in their product for the same reason Nintendo put protection in their products. Sin & Punishment N64 ROM will wipe Doctor V64 BIOS. So, Gateway are acting just as professionally as Nintendo.. right?
 
  • Like
Reactions: wch090 and frown

Site & Scene News

Popular threads in this forum