Hacking R4i Deluxe/3DSLink Firmware V. 3.x release thread

Cyan · Jan 11, 2014

I see.
Maybe their 3.3 is not 3.0 then.
Or maybe they didn't change that string in 3.3b to prevented any bugs in reencrypting, etc., or just did it on a haste.

I don't think we will get an official explanation.
Let's see what gateway team has to say about that bug too.

masterzero · Jan 11, 2014

what games can't play 2.0 /2.1 3dslink/r4i ?¿ ( besides the obvious ones) zelda mh4 only ? can bravely default be played?

Cyan · Jan 11, 2014

bravely default is working with Deluxe/Link v2.0

It doesn't play games with SDK5+
http://wiki.gbatemp.net/wiki/3DS_flashcarts_game_compatibility#Problematic_games
(this chart only list games with SDK5 released before the v3.0)

masterzero · Jan 11, 2014

so only zelda mh4 and batman , well that leaves me way too many games for me to play while we get out of betas XD

hiron · Jan 11, 2014

masterzero can you give the link to the spanish forum? Chrome can translate spanish so thats not a problem.

masterzero · Jan 11, 2014

http://www.elotrolado.net/foro_nintendo-3ds-scene_202

juins · Jan 11, 2014

hmm.
well, i repeat, im on 3.2 and NO issues whatsoever. I dont use emunand with this SD card.

BUT

i do have a 2nd sdcard setup which i use for emunand. I DID notice that while on emunand, 3ds woudnt recover from sleep mode, would stay on a black screen (sometimes, not everytime. Had to hard reset.

Im pretty sure this has something to do with it. It was really weird, even the battery LED went all crazy,alternating from blue to red with very low intensity. This is a normal 3ds.

Maybe if your battery dies while your 3ds is in this state (not being able to resume from sleep mode), this happens? XL exlusive problem from what im reading. Someone with a hardware downgrade accesibility would have to try this out

Its only an issue with emunand tho. Normal loading works 100% fine.

jajasilver · Jan 11, 2014

juins said:
hmm.
well, i repeat, im on 3.2 and NO issues whatsoever. I dont use emunand with this SD card.

BUT

i do have a 2nd sdcard setup which i use for emunand. I DID notice that while on emunand, 3ds woudnt recover from sleep mode, would stay on a black screen (sometimes, not everytime. Had to hard reset.

Im pretty sure this has something to do with it. It was really weird, even the battery LED went all crazy,alternating from blue to red with very low intensity. This is a normal 3ds.

Maybe if your battery dies while your 3ds is in this state (not being able to resume from sleep mode), this happens? XL exlusive problem from what im reading. Someone with a hardware downgrade accesibility would have to try this out

Its only an issue with emunand tho. Normal loading works 100% fine.

Do you have WiFi turned off in your case?

juins · Jan 11, 2014

jajasilver said:
Do you have WiFi turned off in your case?

yes. when im only on realnand and also on emunand.

Although, i did download all the free apps and stuff from eshop, bravely default demo too.

kublai · Jan 11, 2014

R4i keeps locking up on me randomly. I have tried fw 2.0-3.3 with 3 differnt games, 2 different Microsd. I wonder if I have a defective R4i.

juins · Jan 11, 2014

kublai said:
R4i keeps locking up on me randomly. I have tried fw 2.0-3.3 with 3 differnt games, 2 different Microsd. I wonder if I have a defective R4i.

try with another mSD card. in all my use of 3dslink, ive only ever gotten one lockup in castlevania.

U could try formatting your system memory, if u dont mind erasing any of your stuff on the 3ds

jajasilver · Jan 11, 2014

kublai said:
R4i keeps locking up on me randomly. I have tried fw 2.0-3.3 with 3 differnt games, 2 different Microsd. I wonder if I have a defective R4i.

locking up while playing games or booting to menu?
I had these issues on older version but 3.2 fixed them for me. try turning off wifi and rebooting

kublai · Jan 11, 2014

While playing games.

jajasilver said:
locking up while playing games or booting to menu?
I had these issues on older version but 3.2 fixed them for me. try turning off wifi and rebooting

jajasilver · Jan 11, 2014

kublai said:
While playing games.

then I would try another microSD in this case, I know for a fact that SD cards are flaky, especially china fake ones that claim to be some other big brand.

kublai · Jan 11, 2014

I have tried 2 genuine sandisk 16gb cards

kyogre123 · Jan 11, 2014

3.3 just behaves like 3.0/GW2.0b1, but 3.3b is literally the same file that comes with the 2.0 download.

I have only read two well explanations about what caused the bricks and they are these:
First, a Gateway user reported this:
System bricked due to emuNAND overwriting information on the realNAND. After exiting emuNAND, the 3DS couldn't boot again.

R4i users reported:
From the real NAND, accessing "Flashcard" mode from the menu of the launcher caused an error/system freeze (as usually happens when the launcher doesn't boot). The 3DS was shut down, then turned on again and couldn't boot again. This process didn't involve emuNAND as the first one.
----

Remember that save issue that the clones had due to the date of the 3DS? this could be something similar since now everyone is suddenly having this problem with the launcher of the clones and it's not completely related to emuNAND as the case of the Gateway user.

hiron · Jan 11, 2014

kyogre123 said:
R4i users reported:
From the real NAND, accessing DS Profile caused an error/system freeze (as usually happens when the launcher doesn't boot). The 3DS was shut down, then turned on again and couldn't boot again. This process didn't involve emuNAND as the first one.

As far as I know all the users had EmuNAND so it did involve EmuNAND. Yes when you boot profile mode it was in RealNAND but they were all trying to access EmuNAND so its not entirely unrelated.

kyogre123 · Jan 11, 2014

hiron said:
As far as I know all the users had EmuNAND so it did involve EmuNAND. Yes when you boot profile mode it was in RealNAND but they were all trying to access EmuNAND so its not entirely unrelated.

You are right, but what I meant to say is that the problem is not emuNAND writing in addresses of the real NAND, it's just a strange error cause when the menu of the launcher fails to boot after trying to boot it (just like what has been happening since this menu exists in the launcher), but this time, after shutting down the system to reset the console, the damage is done without even getting access to emuNAND.

jajasilver · Jan 11, 2014

kyogre123 said:
You are right, but what I meant to say is that the problem is not emuNAND writing in addresses of the real NAND, it's just a strange error cause when the menu of the launcher fails to boot after trying to boot it (just like what has been happening since this menu exists in the launcher), but this time, after shutting down the system to reset the console, the damage is done without even getting access to emuNAND.

How do you know it doesnt happen before the shutdown (while the console is still running) and you only notice while you boot up next

kyogre123 · Jan 11, 2014

jajasilver said:
How do you know it doesnt happen before the shutdown (while the console is still running) and you only notice while you boot up next

I didn't specifically say that shutting down the console is what is damaging the 3DS. It's exactly that, you notice this after restarting. Again, the weird thing about this is that it doesn't happen after being on emuNAND, it happens when emuNAND fails to launch, something that is not rare at all, however this time there's a damage caused to the System.

Hacking R4i Deluxe/3DSLink Firmware V. 3.x release thread

GBATemp's lurking knight

Well-Known Member

GBATemp's lurking knight

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Mexican Pride

Well-Known Member

Mexican Pride

Member

Mexican Pride

Similar threads

Popular threads in this forum