Hacking r4 deluxe edition help

[kyogre123]

That's my problem. It DOESN'T crash and reboot console. It lets me go into DS profile like normal. Something is wrong with either the gold card or wood firmware and I've tried different woods.

#3

 

[simba115]

#3

Sorry don't understand what I'm supposed to do? GW stands for gateway right? Please excuse my extreme noobness.

 

[kyogre123]

Sorry don't understand what I'm supposed to do? GW stands for gateway right? Please excuse my extreme noobness.

Go to gateway-3ds.com, in the downloads section, there's their firmware. Inside this zip, it's a folder for their blue cart; use the .nds rom with your R4i DS cart to do the DS profile hack. It should work, since the native R4i function in your cart is failing for this.

 

[Bonovox40]

What the heck. Was playing Zelda just fine last night. Now when I click on the DS profile it white stripes and crashes back to the main screen, but it's back to the sysnand 4.4 fw....???

Also, on the emunand side I made a folder (to differentiate) the nand areas, and when I shut down the 3ds, and go back in, that folder has been copied to the same location on the sysnand side. What's up with that?

Formatted the SD card and put a fresh launcher file back on. Maybe I have to install the exploit AGAIN. I'm not sure what the deal was.

Just in case there is an issue with the emunand side, is there a safe way to purge that and rebuild it back to 6.3? I backed up the SD card when I had the "working normally" 6.3 emunand on it, if that matters. If the emunand fw version is stored somewhere else (internally) than idk what's the next safe steps to do. (if things are still wonky after I test the reinstalled launcher)

 

[kyogre123]

Also, on the emunand side I made a folder (to differentiate) the nand areas, and when I shut down the 3ds, and go back in, that folder has been copied to the same location on the sysnand side. What's up with that?

Some changes on Home Menu get copied to the real NAND, such as placing apps inside folders, etc; however the exact order of the apps is not going to be copied if you place stuff randomly.

 

[simba115]

Go to gateway-3ds.com, in the downloads section, there's their firmware. Inside this zip, it's a folder for their blue cart; use the .nds rom with your R4i DS cart to do the DS profile hack. It should work, since the native R4i function in your cart is failing for this.

all I have to do is copy the .nds rom or all the contents of the folder? do I add this .nds rom to the root of my microsd that already has the wood?

 

[kyogre123]

all I have to do is copy the .nds rom or all the contents of the folder? do I add this .nds rom to the root of my microsd that already has the wood?

As I said, just the ROM. Doesn't R4i have instructions on how to boot ROMs with their cart? I don't have this cart, but normally, you create a "Roms" folder to place .nds roms for DS flashcards.

 

[Bonovox40]

Some changes on Home Menu get copied to the real NAND, such as placing apps inside folders, etc; however the exact order of the apps is not going to be copied if you place stuff randomly.

Ok ill try moving some icons around. But why does the ds profile crash now bring me to the sysNAND screen?

 

[kyogre123]

Ok ill try moving some icons around. But why does the ds profile crash now bring me to the sysNAND screen?

I have no idea, check the emuNAND partition with a hex editor, other users may help you to check if somehow it got corrupted.

 

[aiat_gamer]

That's my problem. It DOESN'T crash and reboot console. It lets me go into DS profile like normal. Something is wrong with either the gold card or wood firmware and I've tried different woods.

again, why arent you using the blue card with the firmware provided by the gateway?

 

[Bonovox40]

So if I boot the DS profiler holding L down, I can select "boot gateway/R4i mode" and everything is fine. But I wonder if the reason the default DS profile crash back to just sysnand, is because I did the backup emunand/update to 6.3 using gateway files.

So if I select "format emunand" and this point, do I lose the 6.3 update and revert back to sysnand of 4.4? Can I recover the 6.3 update? (Either with the 6.3 backup emunand I made, or it's still "inside" the 3ds?)

I haven't seen much regarding the format/rebuilding of the emunand AFTER it's already been done once. Not sure the whole progression of events in this case. Thanks!

 

[Nurio]

So if I boot the DS profiler holding L down, I can select "boot gateway/R4i mode" and everything is fine. But I wonder if the reason the default DS profile crash back to just sysnand, is because I did the backup emunand/update to 6.3 using gateway files.

So if I select "format emunand" and this point, do I lose the 6.3 update and revert back to sysnand of 4.4? Can I recover the 6.3 update? (Either with the 6.3 backup emunand I made, or it's still "inside" the 3ds?)

I haven't seen much regarding the format/rebuilding of the emunand AFTER it's already been done once. Not sure the whole progression of events in this case. Thanks!

If you select "Format EmuNAND" now, it will rewrite your current sysNAND to the EmuNAND partition. So, yes, it will revert back to 4.4
Updating your EmuNAND then will cause it to go to 7.0

I've heard some people say they updated through a game cartridge... For example, Pokémon would supposedly update your EmuNAND to 6.1, but that's not something I've been able to confirm.

 

[mr. fancypants]

Inserted gold card.

Removed 3DS SD card, formatted it, put on launcher.dat file.



I can't seem to run the exploit from other settings --> Profile ---> Nintendo DS profile ( it does not restart the console)

Doesnt accept starter cartridge with rom either.

Any ideas? Do I need firmware 4.1 or 4.5 or is mine ok.

did you download the 3.0 .dat file ? if thats the case you need to press L after you pressed on DS settings

 

[Bonovox40]

If you select "Format EmuNAND" now, it will rewrite your current sysNAND to the EmuNAND partition. So, yes, it will revert back to 4.4
Updating your EmuNAND then will cause it to go to 7.0

I've heard some people say they updated through a game cartridge... For example, Pokémon would supposedly update your EmuNAND to 6.1, but that's not something I've been able to confirm.

So at this point, where exactly is the 6.3 emunand stored? (unless it's been corrupted) When I updated successfully to 6.3 emunand, I did a backup of the SD card through windows. (copy the folders/launcher over to PC)

Is the 6.3emunand embedded/saved somewhere on my files or 3ds, to the point where I can recover it if these silly errors continue?

 

[dagro]

So at this point, where exactly is the 6.3 emunand stored? (unless it's been corrupted) When I updated successfully to 6.3 emunand, I did a backup of the SD card through windows. (copy the folders/launcher over to PC)

Is the 6.3emunand embedded/saved somewhere on my files or 3ds, to the point where I can recover it if these silly errors continue?

emunand is a partition on your sd card and you did not back up if you just copied and paste you have to use win32disk imager to read the microsd and make an image which is same size as your sd, backup now while its working and also backup your nand if you fail with some updates atleast you have safety net to fall back on (nand being harder to reinstall then emunand)

 

[Nurio]

Also... As a technicality, the EmuNAND is not a partition. It's the absence of one. It's unallocated space.
...But yes, that's just a technicality.

Bonovox40, do you say you're using an R4i Gold Deluxe, but have an EmuNAND created by Gateway? If so, there might just be a fix... A somewhat complicated one, though.

 

[kyogre123]

Probably, just probably, they just changed the dummy section so a GW emuNAND can't be detected by a clone's emuNAND and vice versa; but the rest of the info may be stored in the exact address for both; so the solution would be just changing the header.

 

[Nurio]

Probably, just probably, they just changed the dummy section so a GW emuNAND can't be detected by a clone's emuNAND and vice versa; but the rest of the info may be stored in the exact address for both; so the solution would be just changing the header.

Yes, that was going to be my suggestion, though I presume he needs a few instructions for that.
But I thought to wait for his confirmation before doing anything like typing out those instructions...

 

[Bonovox40]

Also... As a technicality, the EmuNAND is not a partition. It's the absence of one. It's unallocated space.
...But yes, that's just a technicality.

Bonovox40, do you say you're using an R4i Gold Deluxe, but have an EmuNAND created by Gateway? If so, there might just be a fix... A somewhat complicated one, though.

Yes, I did the emunand creation with gateway files on a R4i deluxe card ONLY to get the 6.3 update before it was too late. (and I just made it by probably 30 minutes)

Anywho, I tried the other day to to a read/backup using the win32disc imager that I used for putting the roms on the microsd card, but I didn't see any options when I hooked up the emunand SD card and started the program. The read option was greyed out. Is there a "full" version I need to use and this is trial/demo, or am I doing something wrong?

It saw the card, just seemed to only have the option to write a rom to it. (which I don't want to do on the SD card of course)

 

[Nurio]

Yes, I did the emunand creation with gateway files on a R4i deluxe card ONLY to get the 6.3 update before it was too late. (and I just made it by probably 30 minutes)

Anywho, I tried the other day to to a read/backup using the win32disc imager that I used for putting the roms on the microsd card, but I didn't see any options when I hooked up the emunand SD card and started the program. The read option was greyed out. Is there a "full" version I need to use and this is trial/demo, or am I doing something wrong?

It saw the card, just seemed to only have the option to write a rom to it. (which I don't want to do on the SD card of course)

To backup using Win32 Disk Imager, you need to insert the SD card and know what drive letter Windows gives it...
Then in Win32 Disk Imager, choose the drive letter from the dropdown menu and press the little folder item to "open" an .img file
Instead of opening a file, simply browse to a directory where you want to save the backup, write a filename for it (like backup.img) and then you can use the Read option

Once you have done that, perhaps I can write something up to change your emuNAND to make it R4i compatible...