Hacking ANNOUNCING: GATEWAY 2.1 "OMEGA" PUBLIC RELEASE

[Queno138]

nope

Thanks mate.
Now I'm gonna try something ><

 

[_Tim_]

Today I received the dreaded "Fragmentation Error" message for the first time. I think I figured out why it happens. I created a small program that scans a microSD card and detects these "errors".

UPDATE 1: I scanned another microSD card and my program reported 3 files with fragmentation errors. Only 1 of them actually triggers the "Fragmentation Error" message on my 3DS. I will have to investigate it further. If anyone has a microSD card with fragmentation errors, PM me.

UPDATE 2: I removed the attached file. Look a few posts down for the new version.

 

[guardianx71]

Today I received the dreaded "Fragmentation Error" message for the first time. I think I figured out why it happens. I created a small program that scans a microSD card and detects these "errors".

Care to elaborate?

 

[Bug_Checker_]

The brick code does exist in 2.1. I have no idea why you're doubting it.
It's in the Launcher.dat at offset 0x25160 size 0xB20. AES key 0x514E7232 0xDD58D52F 0xB1D257D2 0xB65E1CD4.

Here's a quick picture of the code from that region.

Spoiler

What I am doing wrong? I'm trying to checkout the code. I've decrypted the launcher.dat with the key from 2.x.

openssl enc -aes-128-cbc -d -K 580006192800C5F0FBFB04E06A682088 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec.dat
or
enc -aes-128-cbc -d -K 580006192800C5F0FBFB04E06A682088 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec.dat

Then I cut out 0xb20 byte block from Launcher_dec.dat @0x25160 as a filenamed Launcher_dec_0x25160_0xb20.dat .
Then I ran that thru openssl as:
openssl enc -aes-128-cbc -d -K 514E7232DD58D52FB1D257D2B65E1CD4 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20_decrypted.dat
or
enc -aes-128-cbc -d -K 514E7232DD58D52FB1D257D2B65E1CD4 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20_decrypted.dat

But it does not look like your code

Why I am having such a hard time? What have I missed? Is there a middle decryption step I'm missing or additional keys?

 

[Ennea]

Care to elaborate?

Simple: fragmentation. "NO!" Yes! The problem is as the error says, fragmentation. Files residing in non-adjacent blocks in the file system, instead of everything sticking together. Gateway can't handle it. I wouldn't download that program, who knows what's in it..

 

[guardianx71]

Yeah , I know what fragmentation is. I was asking as what his program does? Is it a simple deframenting tool or something else?

 

[Bond697]

What I am doing wrong? I'm trying to checkout the code. I've decrypted the launcher.dat with the key from 2.x.

openssl enc -aes-128-cbc -d -K 580006192800C5F0FBFB04E06A682088 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec.dat
or
enc -aes-128-cbc -d -K 580006192800C5F0FBFB04E06A682088 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec.dat

Then I cut out 0xb20 byte block from Launcher_dec.dat @0x25160 as a filenamed Launcher_dec_0x25160_0xb20.dat .
Then I ran that thru openssl as:
openssl enc -aes-128-cbc -d -K 514E7232DD58D52FB1D257D2B65E1CD4 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20_decrypted.dat
or
enc -aes-128-cbc -d -K 514E7232DD58D52FB1D257D2B65E1CD4 -iv 00000000000000000000000000000000 -nopad -in C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20.dat -out C:\GW_OMEGA_2.1_RELEASE\Launcher_dec_0x25160_0xb20_decrypted.dat

But it does not look like your code

Why I am having such a hard time? What have I missed? Is there a middle decryption step I'm missing or additional keys?

you need to do the decryption with the 3ds hardware. it's key + keyscrambler, slot 0x3D.

 

[db2431]

Can anyone tell me if its safe to install the ds profile exploit with an acekard 2i rather than the black/grey gateway ds cart?I prefer the acekard and don't want to be carrying 3 carts round when I want to go back to 3ds gateway mode from ds mode.

 

[Technicmaster0]

Can anyone tell me if its safe to install the ds profile exploit with an acekard 2i rather than the black/grey gateway ds cart?I prefer the acekard and don't want to be carrying 3 carts round when I want to go back to 3ds gateway mode from ds mode.

The GW_INSTALLER.NDS is a normal DS homebrew.

 

[Snailface]

Can anyone tell me if its safe to install the ds profile exploit with an acekard 2i rather than the black/grey gateway ds cart?I prefer the acekard and don't want to be carrying 3 carts round when I want to go back to 3ds gateway mode from ds mode.

AK2i is only compatible up to v4.4.

 

[db2431]

AK2i is only compatible up to v4.4.

I'm on 4.3

 

[petspeed]

AK2i only support up to 4.3

My 3DS is on 4.4 and my fully updated AK2i doesn't work on it.

 

[Mr_Pichu]

Today I received the dreaded "Fragmentation Error" message for the first time. I think I figured out why it happens. I created a small program that scans a microSD card and detects these "errors".

UPDATE: I scanned another microSD card and my program reported 3 files with fragmentation errors. Only 1 of them actually triggers the "Fragmentation Error" message on my 3DS. I will have to investigate it further. If anyone has a microSD card with fragmentation errors, PM me.

I hear this one works pretty well:
https://www.piriform.com/defraggler/builds

 

[bartimeaus91]

AK2i is only compatible up to v4.4.

You sure? I thought it works up to 4.3 and works on 4.4 only if you use action replay.

 

[Ennea]

I here this one works pretty well:
https://www.piriform.com/defraggler/builds

Don't defrag SD cards.

 

[Vengenceonu]

Gateway sent me an email for those of you having 0000012 and 19 errors with a fix. Here's the link

http://gbatemp.net/threads/diy-how-to-fix-gateway-error-00000012-and-00000019.364622/

 

[gamesquest1]

Gateway sent me an email for those of you having 0000012 and 19 errors with a fix. Here's the link

http://gbatemp.net/threads/diy-how-to-fix-gateway-error-00000012-and-00000019.364622/

That was already shared about a week ago, doesn't work for most people, still waiting on some faulty cards to take a look at

 

[_Tim_]

After spending many hours trying to figure out why some fragmented files trigger the "Fragmentation Error" message and others don't, I think I finally figured it out. I updated my program and it detects with 100% accuracy which files are "bad" on all of my microSD cards. I already have an idea on how to "fix" the microSD card to prevent GW3DS fragmentation errors.

 

[_Tim_]

Care to elaborate?

It looks like a stupid GW3DS exFAT (and maybe FAT32/FAT16 too) FAT table cluster number bug.

 

[_Tim_]

Simple: fragmentation. "NO!" Yes! The problem is as the error says, fragmentation. Files residing in non-adjacent blocks in the file system, instead of everything sticking together. Gateway can't handle it. I wouldn't download that program, who knows what's in it..

Fragmentation itself is NOT the problem. I had files with 5 fragments which loaded just fine.