R4i doesn't read old saved games

Discussion in 'R4 DS' started by JJd2sc, May 22, 2009.

  1. JJd2sc
    OP

    JJd2sc Newbie

    Newcomer
    5
    0
    Mar 14, 2009
    United States
    I recently got a dsi, and bought an r4i ultra. I upgraded my firmware to the latest version, and now my saves are no longer read. The saves are still in the folder, but are not recognized as such when I start the game. Does anyone know anything about this problem?
     
  2. nicky041192

    nicky041192 GBAtemp Maniac

    Member
    1,433
    0
    Mar 9, 2008
    UK
    guaranteed people are gonna say shit about the r4i lol
     
  3. JJd2sc
    OP

    JJd2sc Newbie

    Newcomer
    5
    0
    Mar 14, 2009
    United States
    Maybe, but i have friends that it has worked fine for.
     
  4. nicky041192

    nicky041192 GBAtemp Maniac

    Member
    1,433
    0
    Mar 9, 2008
    UK
    you sure you got the correct firmware?
     
  5. JJd2sc
    OP

    JJd2sc Newbie

    Newcomer
    5
    0
    Mar 14, 2009
    United States
    yes sir, double checked too.
     
  6. JJd2sc
    OP

    JJd2sc Newbie

    Newcomer
    5
    0
    Mar 14, 2009
    United States
    bump
     
  7. Depravo

    Depravo KALSARIKÄNNIT

    Global Moderator
    GBAtemp Patron
    Depravo is a Patron of GBAtemp and is helping us stay independent!

    Our Patreon
    5,238
    3,478
    Oct 13, 2008
    Purgatory
    Try going back to the old firmware if that one worked OK. This is why people advise against buying any of the R4 clones. They're just a bit too... temperamental.
     
  8. Kamika

    Kamika GBAtemp Regular

    Member
    156
    0
    Feb 13, 2009
    Netherlands
    Seems like the latest firmware contains a few BIG bugs so I also advise to downgrade the firmware to the previous version.
     
  9. Maz7006

    Maz7006 iSEXu

    Member
    3,635
    35
    Aug 2, 2008
    .....why on earth are people still using the damn R4, this isn't even from the R4 team ! The only good R4 was the R4 DS, which was the original one. Just go back to the older firmware, and somehow report the bug to R4.