Hi all,
Just got a 3in1 to go along with my R4. Last night, when I was first trying to use it, I got the latest version of GBA Exploader (0.57), and tried running an FFVI Advance backup on it by flashing it to NOR. It ran up to the new game screen fine, and so I quit out to change GBA to play on the bottom screen. When I went to load it again, exploader said it could not find a 3in1.
I let my DS charge overnight with the 3in1 in the slot, and this morning when I tried again, it got detected! I tried FF VI again, and started a new game. It froze up halfway through the intro screen, and when i rebooted my DS, Exploader once again said that it couldn't find my 3in1.
Like I said, using the latest Exploader (both DLDI patched and patched so the R4 won't auto re-patch), and using the latest R4 firmware (version 1.18). Any thoughts on what to try? Could it be a bad rom? Would that be enough to screw up the 3in1 to stop being detected? Or is it a bad 3in1?
Apologies if this has been answered before but I haven't seen this exact problem yet on the board.
Just got a 3in1 to go along with my R4. Last night, when I was first trying to use it, I got the latest version of GBA Exploader (0.57), and tried running an FFVI Advance backup on it by flashing it to NOR. It ran up to the new game screen fine, and so I quit out to change GBA to play on the bottom screen. When I went to load it again, exploader said it could not find a 3in1.
I let my DS charge overnight with the 3in1 in the slot, and this morning when I tried again, it got detected! I tried FF VI again, and started a new game. It froze up halfway through the intro screen, and when i rebooted my DS, Exploader once again said that it couldn't find my 3in1.
Like I said, using the latest Exploader (both DLDI patched and patched so the R4 won't auto re-patch), and using the latest R4 firmware (version 1.18). Any thoughts on what to try? Could it be a bad rom? Would that be enough to screw up the 3in1 to stop being detected? Or is it a bad 3in1?
Apologies if this has been answered before but I haven't seen this exact problem yet on the board.







