Hacking Game updates via eShop

[Xzi]

Is it safe to update a game on a retail cartridge through eShop on emuNAND (classic mode) in order to play it online? The game in question is Pokemon X. I mean, I assume so given that you can buy and download games through the eShop on the latest emuNAND, correct? Just verifying.

 

[JonnyMohawk]

It is safe, I did on my copy of X and it went perfectly fine.

 

[Xzi]

It is safe, I did on my copy of X and it went perfectly fine.

Alright great, thanks. As a quick aside: are you using 2.0b2?

 

[Soul_Alchemist]

Alright great, thanks. As a quick aside: are you using 2.0b2?

I've been using Eshop PKMN-Y 1.2 since December on Emunand 7.1/GW2.0b2. Everything works like it should.

 

[Xzi]

I've been using Eshop PKMN-Y 1.2 since December on Emunand 7.1/GW2.0b2. Everything works like it should.

Cool. Not worried about bricking at all? I reverted back to 2.0b1 after updating emuNAND and Pokemon X for that reason. Everything still works the same except for system settings and the eShop.

 

[JonnyMohawk]

Alright great, thanks. As a quick aside: are you using 2.0b2?

Yep

 

[Soul_Alchemist]

Cool. Not worried about bricking at all? I reverted back to 2.0b1 after updating emuNAND and Pokemon X for that reason. Everything still works the same except for system settings and the eShop.

AFAIK GW has a sanity check:

If the launcher/SD is corrupted or the MD5 check fails, you just get a black screen and need to restart.
If the launcher isn't loaded like it should, you just get a black screen and need to restart.
If emunand isn't loaded like it should, you get just an error message about powering off the 3ds and need to restart.

Obviously, if your launcher is magically modified in a way it magically erases the encrypted security checks while magically letting every other line of (encrypted) code intact (including the evil brick code) and it magically continues like that with no other error whatsoever until the evil random-date brick code is activated, then yes, you could brick your 3DS.

Still, your 3DS or GW could also fail at any moment and brick your 3DS, they're just cheap pieces of mass-produced electronics. Anything can happen at any time.

Warning: Please understand. I'm not saying any GW firmware is 100% safe. I could very well be an evil agent from the GW church trying to brick your 3DS. Don't trust anyone, I'm just speaking for myself. I repeat, I'm not trustworthy, act at your own risk.

Edit: I almost forgot the main reason I don't like 2.0b1, it's way more unstable, it fails a lot when loading the GW menu/GW mode, and it also tends to freeze your console when you close a game (and you can lose the save data of the last game you played if you were using the Red GW card).

 

[Xzi]

AFAIK GW has a sanity check:

If the launcher/SD is corrupted or the MD5 check fails, you just get a black screen and need to restart.
If the launcher isn't loaded like it should, you just get a black screen and need to restart.
If emunand isn't loaded like it should, you get just an error message about powering off the 3ds and need to restart.

Obviously, if your launcher is magically modified in a way it magically erases the encrypted security checks while magically letting every other line of (encrypted) code intact (including the evil brick code) and it magically continues like that with no other error whatsoever until the evil random-date brick code is activated, then yes, you could brick your 3DS.

Still, your 3DS or GW could also fail at any moment and brick your 3DS, they're just cheap pieces of mass-produced electronics. Anything can happen at any time.

Warning: Please understand. I'm not saying any GW firmware is 100% safe. I could very well be an evil agent from the GW church trying to brick your 3DS. Don't trust anyone, I'm just speaking for myself. I repeat, I'm not trustworthy, act at your own risk.

Edit: I almost forgot the main reason I don't like 2.0b1, it's way more unstable, it fails a lot when loading the GW menu/GW mode, and it also tends to freeze your console when you close a game (and you can lose the save data of the last game you played if you were using the Red GW card).

Yeah, I'm simply wary of having any sort of bricking code present on my SD card at all. I guess if and when 2.0b1 causes me enough inconvenience to make it worth risking, I'll upgrade again. So far it definitely seems feature-complete enough for my needs, though. I can probably wait until 2.0 final and hope that they don't include that same bricking code.

 

[morvoran]

Don't trust anyone, I'm just speaking for myself. I repeat, I'm not trustworthy, act at your own risk.

You seem magically trustworthy to me.