I'll try my 2nd 3DS. It's a test system anyways, so no harm in tryingHave you tried to restore it though? To avoid any damage, just make a second backup of the original backup and use the second backup to try to restore your save file.
I'll try my 2nd 3DS. It's a test system anyways, so no harm in tryingHave you tried to restore it though? To avoid any damage, just make a second backup of the original backup and use the second backup to try to restore your save file.
I did, but it's been a day already and I'm not sure I can restore it, I keep hearing about secure values and corrupted saves, as much as possible I'd like to minimize the risk of data corruption.
This is just a theory, but I think this might work.
If your save says it's corrupted, agree to the message deleting your file, and then make sure the new file has saved. Back up the new save file, and then find the secure value (screenshot attached) and add that secure value to your old save that it kept saying was corrupted, and then import it. Again, I haven't tested it but I don't see why it wouldn't work.
When I stated that this might be the secure value, I was confused and thought the secure value was 4 bytes long, but it is actually 8 bytes long. It doesn't seem like this is the secure value, but just a counter of how many times the game has saved.This is just a theory, but I think this might work.
If your save says it's corrupted, agree to the message deleting your file, and then make sure the new file has saved. Back up the new save file, and then find the secure value (screenshot attached) and add that secure value to your old save that it kept saying was corrupted, and then import it. Again, I haven't tested it but I don't see why it wouldn't work.
Si algún hispanohablante me puede ayudar a traducir, se lo agradecería.
Si funciona el archivo *.py, pero por alguna extraña razón, si tienes un save de otro juego (Rumble, ORAS o XY) te tira error. Ayer estuve toda la noche intentando y me daba éste error
También quise intentarlo con mi save de OR y me salía algo parecido
Borré la carpeta savedatabackup de la SD, usé save manager, parché el bin y...
For those who've got savedata corrupted recently using save_manager homebrew, to fix corrupted savedata you have to have your old savedata backup.
1. Try to make savedata corrupted by messing with hex values. Import to Shuffle then play the game and reformat save game when asked.
2. Backup the empty savedata to the game using save_manager
3. Using hex editor select and copy Offset 0 to 46 from the empty savedata backup, paste exactly the same offsets to your old savedata backup.
4. Import edited savedata to the game using save_manager
5. Profit
Is anyone else having the problem where the save file that's backed up is always a lot older than what's actually going on in the game?
Okay now I'm getting this and it won't go away
What other things should I change for other things? Like what if I want max coins?Try to edit it manually. Replace the byte at 0x2d4b and set it to 0x31, this will give you 98/99 lives.
Indeed, I would not use the Python script. Setting everything to 0xff it's a bad idea, you may be killing some important bits or glitching the savegame.
This works, but it leaves me at level 6, the pidgey stage no matter what save I use.. huh
And that's why I said it's not a good idea to touch unknown bytes.I have been able to make it work properly but, once I have used all of my Megaturbos, I have done the same process again but there are no more Megaturbos! Can anyone please help me with this? Everything else works properly but no Megaturbos :'(
For those who've got savedata corrupted recently using save_manager homebrew, to fix corrupted savedata you have to have your old savedata backup (or savedata from your friend, other sources etc...)
1. Try to make savedata corrupted by messing with hex values. Import to Shuffle then play the game and reformat save game when asked.
2. Backup the empty savedata to the game using save_manager
3. Using hex editor select and copy Offset 0 to 46 from the empty savedata backup, paste exactly the same offsets to your old savedata backup.
4. Import edited savedata to the game using save_manager
5. Profit
Tested and worked.
View attachment 24390
But are you back to where you were?Thanks for testing, my corrupted save is now working again.
Yes, I originally made a initial save backup that where I copied the new offsets to.But are you back to where you were?
does this work with the hombrew saveFor 99'999 Gold/Coins and 150 Diamonds, 99 Bonus and 99 MegaSpeedup with any save backup from SaveDataFiler or the Ninjhax SaveDataTool here with Pokémon Shuffle.
Tested and also runs on the latest 1.2.14 release.
!!! ALWAYS MAKE A CLEAN BACKUP OF YOUR SAVEFILE BEFORE !!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For SaveDataFiler users:
1) Download Pokémon Shuffle Save Patcher.
2) Start the exploit that you use to use SaveDataFiler.
3) In the User tab, scroll down until you find the line 01410. Highlight this line in yellow.
4) Press Y to export the save, and A to confirm.
5) Close SaveDataFiler and turn off your 3DS.
6) Put the SD in the PC.
7) At the root of your SD, navigate to the following folder:
E:\filer\UserSaveData\<DATE>\00001410
7) Put the Python Script here. Drag&Drop the savedata.bin on the Python Script. Wait. Delete the Python Script. Or move it somewhere else.
If you want the OffSets, here: 6A, D1, D2, D3, D4, D5, D6, D7 and 2D4C. The values to these OffSets are destined to be replaced by FF.
8) Remove the old savedata.bin file, and replace it with the new one you just modified.
9) Start the exploit that you use to use SaveDataFiler, and start SaveDataFiler.
10) In the User tab, scroll down until you find the line 01410. Highlight this line in yellow.
11) Press R+X at the same time to delete the Secure Value (Important), then A to confirm the deletion.
12) In the SD tab, scroll down until highlight this line:
user : <DATE> : 00001410
13) Highlight this line. Whatever the numbers, you must highlight the line with 00001410.
14) Press R+A at the same time to import the modified save, then A to confirm.
For Ninjhax SaveDataTool users:
For now, I can't have the tool working...
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Check your game.
For those who've got savedata corrupted recently using the SaveManager homebrew:
@thaikhoa said:
For those who've got savedata corrupted recently using save_manager homebrew, to fix corrupted savedata you have to have your old savedata backup (or savedata from your friend, other sources etc...)
1. Try to make savedata corrupted by messing with hex values. Import to Shuffle then play the game and reformat save game when asked.
2. Backup the empty savedata to the game using save_manager
3. Using hex editor select and copy Offset 0 to 46 from the empty savedata backup, paste exactly the same offsets to your old savedata backup.
4. Import edited savedata to the game using save_manager
5. Profit
Tested and worked:
If you do not have this value, simply use a unit value for make it back to the real number you have.
Repeat the process if you want.
Thanks to @Brewzip for the Offsets.
Thanks to @Doumekxkai for the Python Script.[/URL]
Thanks to my friend for the Windows Version.
Since nobody's posted this here yet...a better python script was posted to 4chan's shuffle thread yesterday: http://pastebin.com/HJQFnwnx