Hacking R4i Gold 3DS Deluxe team totally screwed us

[TDK11]

So I got myself setup with a R4i Gold Deluxe two days ago (luckily just in time to run Gateway and make an emunand partition) However I have to wonder with the 7.0 update out, what's the point of a 3.0 update? Is there anyway I can use my Gateway emunand partition with the R4i update? I tried switching the launcher with the new R4i Gold one, but it didn't work.

I mean I even bought a retail copy of Pokemon Y so I could play in classic mode, using one SD card for Roms (R4i Launcher) and another to play retail carts (Gateway launcher)

Perhaps I'm stuck with the inconvenience of constantly switching between these two cards. And that doesn't even begin to solve the issue of how to play 6.3 ROMS

Halp

 

[Costello]

what did you expect from a clone team, especially one that decides to call their product "R4i 3DS Gold Deluxe Edition" ?

 

[TDK11]

Hey man, if I could do it all again I would have paid the extra for the Gateway 3DS. It's too late for all that now I guess. So disappointed in you R4 team, hopefully there's a fix though.

 

[Schizoanalysis]

Hey man, if I could do it all again I would have paid the extra for the Gateway 3DS. It's too late for all that now I guess. So disappointed in you R4 team, hopefully there's a fix though.

You paid for a clone. You got a clone. Simple.

 

[tranfeer]

What did you do?
Run R4i on the partition created by gw?
You should create it unsing the firmware released by the official website.

 

[kyogre123]

You may modify the emuNAND partitions via hex edit so you can make it compatible with the lame clone cart.

 

[TDK11]

What did you do?
Run R4i on the partition created by gw?
You should create it unsing the firmware released by the official website.

I tried running my Pokemon cart using the Gateway emunand SD card with the updated R4i launcher, but it didn't work. When I launched Pokemon it prompted me to update to 6.1. If I run a ROM, say Zelda: A Link Between Worlds will I encounter the same issue? Or are the ROMs patched to bypass the update prompt or something like that?

You may modify the emuNAND partitions via hex edit so you can make it compatible with the lame clone cart.

Is there a guide or something out there on how to do this exactly?

I'm not very competent with all of this flashcart stuff yet, sorry

 

[kyogre123]

I tried running my Pokemon cart using the Gateway emunand SD card with the updated

Is there a guide or something out there on how to do this exactly?

I'm not very competent with all of this flashcart stuff yet, sorry

No, sorry, but you may need to create an emuNAND partition with the launcher of your cart first, then check the partitions with a hex editor. SOmeone on the forum may give you a hand after you post the details.

By the way, do this using two different SD cards or back up your current emuNAND partition first.

 

[Schizoanalysis]

Is there a guide or something out there on how to do this exactly?

I'm not very competent with all of this flashcart stuff yet, sorry

R4i will release a guide one week after someone else does... the exact same guide, just with an R4i label stuck over it.

 

[TDK11]

R4i will release a guide one week after someone else does... the exact same guide, just with an R4i label stuck over it.

Haha, I get it, the R4i team are clones lol. I get it.

 

[TDK11]

No, sorry, but you may need to create an emuNAND partition with the launcher of your cart first, then check the partitions with a hex editor. SOmeone on the forum may give you a hand after you post the details.

By the way, do this using two different SD cards or back up your current emuNAND partition first.

Alright, so if I understood correctly I'm going to create an emuNAND partition using the Gate-oops I mean R4i 3.0 menu, post the details of that dump I see in a hex editor, and then hope someone on here can help me out.

Also, I've already backed up my Gateway partition, I gave it a 3ds extension, would that do for when/if I wrote it back onto the card?

 

[RenegadeKid]

It was expected dude, sorry for you.

 

[kyogre123]

Alright, so if I understood correctly I'm going to create an emuNAND partition using the Gate-oops I mean R4i 3.0 menu, post the details of that dump I see in a hex editor, and then hope someone on here can help me out.

Also, I've already backed up my Gateway partition, I gave it a 3ds extension, would that do for when/if I wrote it back onto the card?

The extension doesn't matter, just take in account that you may need to create an image file of the emuNAND partition alone, because I'm guessing you backed up the whole SD, including the regular partition, which is completely fine at the moment.

 

[PZ-powa]

I have the exact same problem, I can't run my gateway emunand partition using the R4i launcher.

Hopefully you will find a solution. But yeah, I should have bought a gateway... Uploading the 3.0 update the day after the nintendo update, they couldn't have found a better timing.

 

[n1ghty]

I could add the converting of the emuNAND SDs to my tool, once I finally manage to release it.
The R4i team probably only changed a string...
I am currently at work and have to work overtime to "earn" my holiday.

 

[Quicksilver88]

Well....I actually have a Gateway and made EmuNand 6.3 partitions for both my 3DS and XL and it is working fine....I ordered a cheap r4 (because I have two 4.5 3DSes) so I hope they come out with a hex fix or better yet hopefully r4 and Gateway teams will figure out a way to do the emunand update step from a cartridge. Surely something will come out with 6.3 soon as the update partition and then maybe the update will work that way......I am really starting to believe r4/dslink are ripping off Gateway's software because everyone knew Nintendo was doing an update this month, Gateway released so people could get 6.3 while it was out, why didn't the cloners get their udpate out in time......my guess because it took every last second to modify the Gateway release.

Oh well I only paid like less than $40 for the clone so even if I can't emunand I will still get some use out of it....still these teams need to step it up as having Nintendo release new firmware before they release their patches for the current firmware isn't very ideal.

 

[TDK11]

The extension doesn't matter, just take in account that you may need to create an image file of the emuNAND partition alone, because I'm guessing you backed up the whole SD, including the regular partition, which is completely fine at the moment.

Oh, yeah I did haha, guess I might need to find a way to backup the partition only if I wanna transfer from 4gb to 2gb SD card. By the way is there anyway to write the NAND.bin back onto the 3DS as of right now?

I could add the converting of the emuNAND SDs to my tool, once I finally manage to release it.
The R4i team probably only changed a string...
I am currently at work and have to work overtime to "earn" my holiday.

I bet that'd be a tremendous help to a lot of us

 

[kyogre123]

Oh, yeah I did haha, guess I might need to find a way to backup the partition only if I wanna transfer from 4gb to 2gb SD card. By the way is there anyway to write the NAND.bin back onto the 3DS as of right now?

Only via hardware mod. This file is there in case you update the actual NAND of your 3DS; without this backup, it's impossible to downgrade.

 

[TDK11]

Only via hardware mod. This file is there in case you update the actual NAND of your 3DS; without this backup, it's impossible to downgrade.

Yeah, I figured as much. I was wondering so I could be prepared for that worst case scenario

I really appreciate all of the help, I've noticed you've been saving lives everywhere in the community. I don't know what we'd do without you

I have the exact same problem, I can't run my gateway emunand partition using the R4i launcher.

Hopefully you will find a solution. But yeah, I should have bought a gateway... Uploading the 3.0 update the day after the nintendo update, they couldn't have found a better timing.

I know the feel man, at least we have a useful emuNAND partition at all, as opposed to a bunch of people who now can't update to 6.3

 

[Cyan]

With a chance, you only need to edit the first sector (MBR/Dummy sector).
You don't need to backup and restore the full dump.

After you created your EmuNAND SDCard, you can use an Hexeditor to "open device" (not the partition), select the SD card, and look at sector 0.

The first sector of a Gateway EmuNAND partition looks like that:

GATEWAYNAND - THIS IS DUMMY SECTOR, SEARCH FOR "NCSD" FOR REAL SECTOR

00000000 4741 5445 5741 594E 414E 4420 2D20 5448 GATEWAYNAND - TH
00000010 4953 2049 5320 4455 4D4D 5920 5345 4354 IS IS DUMMY SECT
00000020 4F52 2C20 5345 4152 4348 2046 4F52 2022 OR, SEARCH FOR "
00000030 4E43 5344 2220 464F 5220 5245 414C 2053 NCSD" FOR REAL S
00000040 4543 544F 5200 0000 0000 0000 0000 0000 ECTOR...........
00000050 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000060 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000070 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000080 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000090 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000A0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000B0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000C0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000D0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000E0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000F0 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000100 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000110 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000120 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000130 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000140 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000150 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000160 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000170 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000180 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000190 0000 0000 0000 0000 0000 0000 0000 0000 ................
000001A0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000001B0 0000 0000 0000 0000 0000 0000 0000 0001 ................
000001C0 0100 0CFE FFB7 0000 2000 0020 C900 0000 ........ .. ....
000001D0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000001E0 0000 0000 0000 0000 0000 0000 0000 0000 ................
000001F0 0000 0000 0000 0000 0000 0000 0000 55AA ..............U.