Corrupted SAVs?

Discussion in 'Other Flashing Hardware & Software' started by jesterscourt, Apr 21, 2007.

Apr 21, 2007

Corrupted SAVs? by jesterscourt at 5:44 PM (6,638 Views / 0 Likes) 23 replies

  1. jesterscourt
    OP

    Member jesterscourt Not Brad.

    Joined:
    Jan 3, 2007
    Messages:
    2,153
    Country:
    United States
    Seeing as there is no ROM talk on the official forums, I suppose this would be the best place to ask.

    Certain games seem to either not save properly, or revert to an older save (or a non-save)

    These are covered on the Compatibility wiki such as Hotel Dusk and Custom Robo Arena... is there anything I can do about it however? I will be playing for hours, go to save, turn it back on, it saves the EEPROM data, I go back into the game, and then I am at the beginning... [​IMG]
     


  2. ChuckMcB

    Member ChuckMcB GBAtemp Fan

    Joined:
    Mar 30, 2007
    Messages:
    373
    Country:
    United Kingdom
    CRA's saves seem to get messed up when you play another game then go back to it. For a while there I backed up the save every time I played it....but it was too much hassle, now I just play online.

    When the new Firmware comes out I'll start back into these games again.
     
  3. freakygeeky

    Newcomer freakygeeky Member

    Joined:
    Dec 6, 2006
    Messages:
    44
    Country:
    United States
    It would be nice if they released that firmware soon, or at least indicated what new features it provides.
     
  4. alanchiz

    Newcomer alanchiz Advanced Member

    Joined:
    Nov 13, 2006
    Messages:
    50
    Country:
    United Kingdom
    Im hoping that the next firmware will sort this too, that said, the only problem I had recently was Theme Park.
    God knows when the FW will come out though, unfortunately I have no faith left in the DS-X team.
     
  5. ChuckMcB

    Member ChuckMcB GBAtemp Fan

    Joined:
    Mar 30, 2007
    Messages:
    373
    Country:
    United Kingdom
    Since it's only a 0.0.1 release (v1.1.0 to v1.1.1) I can't see too many changes taking place, but I'm sure the DS-X team know it's in their best interest to get as many of the current bugs sorted as soon as possible.

    I've got a couple of new games myself that I can't be bothered playing as I lost a couple of hours play due to save problems.
     
  6. kazumi213

    Member kazumi213 GBAtemp Regular

    Joined:
    Oct 16, 2006
    Messages:
    293
    Country:
    Spain
    Here are my conclusions about the save corruption problem on the DS-X.

    The cause is the "EEPROM contents to .SAV file" writting routine (EEPROM message at bootup) is just half-baked for at least the FLASH-type saves. For some FLASH 2 Mbit games (like Mario Kart and Metroid PH) the current DS-X routine correctly writes EEPROM contents to a .SAV file and the result is a WORKING .SAV file.

    However for other FLASH 2 Mbit games (Pokemon Ranger and Pokemon D/P) the routine creates CORRUPTED, NON-WORKING .SAV files, there's no such "after you play other ROM" corruption cause, the .SAV is simply created in a corrupted state.

    Now some of you will say: but if I keep playing Pokemon Ranger without playing other ROM, my saves work. The answer is no. Each time you see the EEPROM message a corrupted .SAV file is being created. What happens is that the (working) EEPROM contents are not being completely flushed (cleaned) when the .SAV file is create so when you go back and continue your Pokemon Ranger game it reads the EEPROM contents, not the recently created .SAV file. However if you play other ROM, EEPROM contents gets replaced. When you come back to Pokemon Ranger now it can't read from the EEPROM so it tries to read from your .SAV. But your .SAV has been created corrupted (not corrupted by playing other ROM), so that's why you get the corruption message in Pokemon Ranger.

    This also happens to Pokemon D/P, the DS-X is also creating corrupted .SAV files. But for some reasons these games "fill" the DS-X EEPROM in such a way that their data is not lost when playing another ROM. So as long as they can read from the EEPROM contents you don't have save problems. I've not tested Custom Robo Arena but that "my progress revert to an old state" my be well due to that old state being the only availabe on the EEPROM and the current being lost or saved to a corrupted .SAV file.

    To check this I performed the following test: I played Pokemon D for about 1 hour 15 min. The last in-game save I made was repeated 4 times in a row just to be sure the EEPROM only contained data pertaining to that save. The EEPROM message appeared and my .SAV file was updated. BEFORE loading again Pokemon D, I copied (not cut) the .SAV from my DS-X to my HD. Then I played again Pokemon D. No problems.

    Then I deleted the .SAV from my DS-X and loaded Pokemon D. As many have already experienced, you can continue to play even without that .SAV present, a proof it is reading EEPROM contents. I loaded again Pokemon D, but this time at titlescreen I used UP+SELECT+B to ERASE any trace of my progress. This effectively flushes the EEPROM because next time I load Pokemon D it directly starts a new game.

    Ok then: I perform the erasing process again but I don't start a new game. I just shut down my NDSL and copy my backup .SAV to the DS-X. Know what? The game says my save is corrupted (remember it was suppossedly working whan I backuped it and before doing all that erasing stuff).

    To eliminate all possible interaction I performed then a more extreme test: reflash my DS-X firmware. I know this effectively flushes ALL EEPROM contents. Also I low level formatted the card. The idea was to be sure there was no trace of Pokemon D.

    The result is: while restored backup .SAV files for Mario Kart and Metroid PH are working after all this, the Pokemon D .SAV is not recognized and the corrupted message appears.

    As I said the corruption problem for some FLASH-type saves is caused by a half-baked FLASH save writting support in the DS-X.

    Hope this and MANY other ROM issues/annoyances get fixed FIRST, before releasing a new and unnecessary bells & whistles GUI and more useless SkinApps. And please, DS-X team test your firmware before release and I mean test it seriously.
     
  7. bragon

    Newcomer bragon Newbie

    Joined:
    May 3, 2007
    Messages:
    8
    Country:
    Canada
    I was afraid to loose my 11 hours of play to Pokemon D in DS-X. So I did all the procedure described by Kazumi213 and fortunatelty my Pokemon D save was not corrupted. I dit it two times because the first time I did not erase the eeprom twice as he described. I also converted the DS-X save to ezflash V save with Shuny’s program and could use it in ezflash V, but only after many tries. In fact, the ezflash V seems to have the same eeprom problem as DS-X. I mean : it is very difficult to have it to use the new save instead of the eeprom save. I had to flush the eeprom by playing a couple of other games.
     
  8. StacMaster-S

    Member StacMaster-S GBAtemp Fan

    Joined:
    Mar 16, 2007
    Messages:
    367
    Location:
    Albany, NY
    Country:
    United States
    Ugh, I'm so pissed off because Pearl was running perfectly fine on the previous firmware, and now I have to wait for a fix and there seems to be no way to get the old firmware software anymore.

    I'm really disappointed with the DS-X team... I got a 4Gb at launch and had practically no issues... now I've got a 16Gb and a 4Gb with the latest firmware and I've got tons of bugs. >____
     
  9. HBK

    Member HBK Clover - Fearless to Speak Now. ;)

    Joined:
    Mar 30, 2007
    Messages:
    1,813
    Location:
    Portugal
    Country:
    Portugal
    StacMaster-S, you can downgrade if you want. Just go to GBATemp's download Center and download the old firmware updater. Follow the basic steps you do when updating, copy the 1.1.0 skin, and voilá.

    Worked for me, went straight back to 1.1.0, Pokemon Diamond/Pearl working perfectly.

    I was a beta-tester of 1.1.2, and it had a lot of problems, though I didn't detect the corruption issue until after public release.
     
  10. StacMaster-S

    Member StacMaster-S GBAtemp Fan

    Joined:
    Mar 16, 2007
    Messages:
    367
    Location:
    Albany, NY
    Country:
    United States
    When did you last use 1.1.0? From what I understand DS-X has taken their older binaries offline, so now the updater can't grab them anymore.
     
  11. HBK

    Member HBK Clover - Fearless to Speak Now. ;)

    Joined:
    Mar 30, 2007
    Messages:
    1,813
    Location:
    Portugal
    Country:
    Portugal
    May 16th, around there.
     
  12. windrider

    Newcomer windrider Member

    Joined:
    Jun 13, 2007
    Messages:
    30
    Location:
    Alberta
    Country:
    Canada
    So with the downgrading is your Pokemon/D/P still working fine. I am thinking also of downgrading just to get those 2 games working. Everything works fine on mine with the latest firmware except those 2 saves.
     
  13. ChuckMcB

    Member ChuckMcB GBAtemp Fan

    Joined:
    Mar 30, 2007
    Messages:
    373
    Country:
    United Kingdom
    You can't go back to v1.1.0 all update apps have been taken offline as people with the new 4Gb cards where breaking their cards by applying v1.1.0 to them (the new cards can only run v1.1.1 or greater)
     
  14. windrider

    Newcomer windrider Member

    Joined:
    Jun 13, 2007
    Messages:
    30
    Location:
    Alberta
    Country:
    Canada
    Yes I should have asked what size card he had, cause I thought I had read that on the DS-X forum.
    Guess I will just wait for the new firmware then, they are getting close.
     
  15. ChuckMcB

    Member ChuckMcB GBAtemp Fan

    Joined:
    Mar 30, 2007
    Messages:
    373
    Country:
    United Kingdom
    Yup, the new Firmware is being Beta tested at the moment.
     
  16. jesterscourt
    OP

    Member jesterscourt Not Brad.

    Joined:
    Jan 3, 2007
    Messages:
    2,153
    Country:
    United States
    I missed this before, but this is one great post. Thank you. [​IMG]
     
  17. kazumi213

    Member kazumi213 GBAtemp Regular

    Joined:
    Oct 16, 2006
    Messages:
    293
    Country:
    Spain
    Thanks jesterscourt. After that post I made further testing which showed slightly different results, like the Pokemon D/P .SAV NOT being always created in a corrupt state, but just sometimes (ramdomly) Anyway this was still bad.

    After that I wrote several posts at DS-X forum regarding the EEPROM issues. A few days after DS-X team were announcing that quick (and barely tested) 1.1.2 firmware which contained the EEPROM fix, but used an updater which proved to be conflicting with the new 16 Gb models. Now they're about to release a new firmware after a 5-6 days public betatesting process.

    However there are 2 games with known saving problems which nobody seem to have tested with the 1.1.2 (for those who say it is working flawlessly): Bleach DS 2nd and Pokemon Ranger. At least the Scorpei compat. list has not been updated about those. So if anyone is betatesting the new firmware and read this, please check those 2 games.
     
  18. D3R3LIC7

    Newcomer D3R3LIC7 Member

    Joined:
    Apr 24, 2007
    Messages:
    45
    Location:
    Texas
    Country:
    United States
    Man this thread was very informative. I have a DS-X and have been getting save corruptions with newer firmwares. Thank goodness it will all be forgotten once I get my R4. It's good to understand your problems though...
     
  19. hicpotboy

    Newcomer hicpotboy Newbie

    Joined:
    Jun 21, 2007
    Messages:
    2
    Country:
    Canada
    One question for you, Kazumi. You seem to know a whole lot about how the DS-X does it's saving. I just downloaded the .sav editor for Pokemon, and while it can't read the actual .sav, if I convert it to something else, it can. Does this mean the save is good, or what?
     
  20. kazumi213

    Member kazumi213 GBAtemp Regular

    Joined:
    Oct 16, 2006
    Messages:
    293
    Country:
    Spain
    No it doesn't. Pokesav can read the uncompressed ("converted") DS-X save even when the save itself is corrupted. I've verified this point. Information like the displayed on Pokesav main window is readable on all corrupted saves that I've tested. However, box pokemon information is screwed.

    To be sure whether your save is ok you must try to load it on a emulator. I recommend using latest no$gba v2.4b. You have to use the uncompressed DS-X save, the same you are currently loading on Pokesav.

    Edit NO$GBA.INI file and search the line where it says:

    SAV/SNA File Format == Compressed

    and change it to

    SAV/SNA File Format == Uncompressed

    Save the edited NO$GBA.INI.

    Now put your uncompressed pokemon save on the "BATTERY" folder and name it the same as the pokemon ROM you are going to load on the emulator.

    If you don't get any error when trying to load your save on no$gba emulator, you can be sure your save is ok. Then you can edit it on Pokesav (don't use the one on BATTERY folder).

    Copy your edited pokemon save to your DS-X just like it comes out from Pokesav.
     

Share This Page