Hacking weird japanese message after updating Omega Ruby.

[Silver-Tiger]

hi guys,

after booting into classic mode using this guide I got this strange message:

anybody knows what this means? And how I can play omega ruby again? I downloaded the update straight from the eshop. I also tried installing it via cia, both no luck. Deleting the update and reinstalling didn't help either.

 

[plasma]

hi guys,

after booting into classic mode using this guide I got this strange message:

anybody knows what this means? And how I can play omega ruby again? I downloaded the update straight from the eshop. I also tried installing it via cia, both no luck. Deleting the update and reinstalling didn't help either.

If i am correct, it is saying your save file is corrupt

 

[DavidKang]

hi guys,

after booting into classic mode using this guide I got this strange message:

anybody knows what this means? And how I can play omega ruby again? I downloaded the update straight from the eshop. I also tried installing it via cia, both no luck. Deleting the update and reinstalling didn't help either.

The save is corrupted. If you played your game above 6.x before on sysnand and you downgraded, even if you have the latest emunand it will be corrupt. It's because of the different save encryption since 6.x I believe? To fix this you should go back to above 6.x if you had made a back up or update with a game.

 

[Silver-Tiger]

If i am correct, it is saying your save file is corrupt

how could this be? I didn't even insert the cardridge other than in classic mode.

 

[wbsddgg]

cant c the pic clearly. im on mobile
and i wish i could see it

 

[plasma]

how could this be? I didn't even insert the cardridge other than in classic mode.

If you are on sysNAND 4.5 and EmuNAND higher than that, and load a game using the 6.x encryption, then Classic mode will load it using the 4.x keys, which results in save file deletion

 

[Silver-Tiger]

The save is corrupted. If you played your game above 6.x before on sysnand and you downgraded, even if you have the latest emunand it will be corrupt. It's because of the different save encryption since 6.x I believe? To fix this you should go back to above 6.x if you had made a back up or update with a game.

I have 2DS, too, and on this one, the save works just fine.

 

[plasma]

I have 2DS, too, and on this one, the save works just fine.

The save will delete if you are running it on a 2/3ds with a sysNAND of 4.x.
Even through classic mode.

 

[Silver-Tiger]

If you are on sysNAND 4.5 and EmuNAND higher than that, and load a game using the 6.x encryption, then Classic mode will load it using the 4.x keys, which results in save file deletion

So how is classic mode useful if you can't play games higher than 6.x encryption?

 

[DavidKang]

I have 2DS, too, and on this one, the save works just fine.

Yes, above 4.5 I believe? It's because of the different save encryption used since 6.x.

 

[Silver-Tiger]

The save will delete if you are running it on a 2/3ds with a sysNAND of 4.x.
Even through classic mode.

Guess I was lucky, then, because the save is still there when using the cardridge on my 2DS.

 

[DavidKang]

So how is classic mode useful if you can't play games higher than 6.x encryption?

You can still play, but you have to delete your save if you played on it above 6.x before. On the first time, yes, you can play. And Games that don't need 6.x or higher will not get corrupted.

 

[osm70]

So how is classic mode useful if you can't play games higher than 6.x encryption?

You can, but if you do you CANNOT use the same game card in retail 3DS.

 

[YourHero]

So how is classic mode useful if you can't play games higher than 6.x encryption?

You can if the sysnand was 6.0 or higher. You obviously downgraded. It's one of the draw backs.

 

[kamesenin888]

hi guys,

after booting into classic mode using this guide I got this strange message:

anybody knows what this means? And how I can play omega ruby again? I downloaded the update straight from the eshop. I also tried installing it via cia, both no luck. Deleting the update and reinstalling didn't help either.

Dude use savedatafiler to backup the save before deleting it then start a new game and inject the main file from the save you backuped and you will be fine if using a 3dz with cia this doesn't work

 

[mvmiranda]

hi guys,

after booting into classic mode using this guide I got this strange message:

anybody knows what this means? And how I can play omega ruby again? I downloaded the update straight from the eshop. I also tried installing it via cia, both no luck. Deleting the update and reinstalling didn't help either.

Ok!
Classic mode uses your sysNAND keys to load games.
This means if your sysNAND is bellow 7.X, your original cart has a save created in an 7.X firmware, your classic mode (even if it's 9.4 and it was "based" on a sysNAND 7.X) will not be able to load this save.

source: myself!
I did a hell of a job updating my 4.5 console to 7.2 using this Pokemon OR, creating a brand new emuNAND based on 7.2, extracting XORPADs and FAT16, decrypting my FAT16, finding all of the saves, encrypting it again, injecting new FAT16 to my emuNAND, injecting emuNAND to SD Card and reverting my sysNAND to 4.5. All of this to have a "brand new 7.x based emuNAND in 9.4 with all of my saves" thinking I could play my Pokemon on classic mode while having an "easy way" of entering emuNAND (using the DS profile exploit) but in the end I discovered that your emuNAND does not matter but your sysNAND.

So, unless you update your sysNAND to 7.X, you will not be able to load this cart in your classic mode.

Cheers!

 

[MrJason005]

Ok!
Classic mode uses your sysNAND keys to load games.
This means if your sysNAND is bellow 7.X, your original cart has a save created in an 7.X firmware, your classic mode (even if it's 9.4 and it was "based" on a sysNAND 7.X) will not be able to load this save.

source: myself!
I did a hell of a job updating my 4.5 console to 7.2 using this Pokemon OR, creating a brand new emuNAND based on 7.2, extracting XORPADs and FAT16, decrypting my FAT16, finding all of the saves, encrypting it again, injecting new FAT16 to my emuNAND, injecting emuNAND to SD Card and reverting my sysNAND to 4.5. All of this to have a "brand new 7.x based emuNAND in 9.4 with all of my saves" thinking I could play my Pokemon on classic mode while having an "easy way" of entering emuNAND (using the DS profile exploit) but in the end I discovered that your emuNAND does not matter but your sysNAND.

So, unless you update your sysNAND to 7.X, you will not be able to load this cart in your classic mode.

Cheers!

but, on gateway ultra, when i load classic mode, it has a black theme (i seperated my nands, sysnand has red theme, emunand has black theme)
so, classic mode uses emunand?

 

[mvmiranda]

but, on gateway ultra, when i load classic mode, it has a black theme (i seperated my nands, sysnand has red theme, emunand has black theme)
so, classic mode uses emunand?

It doesn't matter...
My sysNAND and emuNAND are separated as well.

I'm talking about keys to decrypt saves

 

[MrJason005]

It doesn't matter...
My sysNAND and emuNAND are separated as well.

I'm talking about keys to decrypt saves

but if i had a 5.X sysNAND and a 9.5 emuNAND, it would be a problem
what i'm asking is this: does classic mode use sysNAND or emuNAND?

 

[mvmiranda]

but if i had a 5.X sysNAND and a 9.5 emuNAND, it would be a problem
what i'm asking is this: does classic mode use sysNAND or emuNAND?

Classic Mode uses everything from emuNAND (files, config, themes, etc) BUT keys, which it uses the ones from sysNAND.