Hacking Eshop Broken

  • Thread starter Thread starter LuigiXHero
  • Start date Start date
  • Views Views 3,469
  • Replies Replies 24

LuigiXHero

Well-Known Member
Member
Joined
Dec 16, 2014
Messages
205
Reaction score
154
Trophies
2
XP
1,349
Country
United States
So I've had my 3DS hacked since the days of rxTools and Emunand and ever since I hacked it my eshop hasn't worked. It spits out an error. I'm on current Firmware + AL9H and it still doesn't work. Also everything else relating to the eshop doesn't work either but I can still play online. Did anyone else have this problem and is it fixable?

Edit: This was fixed, check the featured post.
 
Last edited by LuigiXHero,
If your emuand was connected to an nnid, while your sysnand had also an nnid the eshop does not work on sysnand. The solution is to format the 3ds
 
Is there a way to keep my nnid? This is my origianl nnid since I first got my 3ds.
You can set up a new emuNAND (either on the same card after backing up the emunand.bin and card contents or on a separate SD card), log in to your NNID on that and it should automatically work on your previous emuNAND.
 
Well I don't intend on ever going back to emuNAND but I had these games bought since I owned my DSI. I might have a backup somewhere of my sysnand before I did emunand stuff.
 
Which error code?
This is a good question OP should answer.

For I know, there is a specific error code ONLY displayed on a 3DS with other 3DS's MOVABLE.SED manually injected.
In this case, until the original MOVABLE.SED to be restored, the specific error code will continue displaying even you formatted the 3DS.
 
Last edited by MelonGx,
I already am using freeshop but I wNt access to eshop for redownloading things and for themes downloding
you can do all of that in freeshop, but if you want help with eshop you should tell us the error code

Sent from my LG-D852 using Tapatalk
 
Sorry it took so long, the error code is:

022-2634

The error message is the generic, an error has occurred, please try again.
 
I'm pretty sure I had this issue and error code a long time ago back when I set up my first emuNAND. I fixed it by backing up my NAND, using the TinyFormat homebrew to format my NAND, then set it up as a new 3DS, signed into my NNID on the fresh format, then once it was signed in and confirmed working, I restored my NAND backup and it all worked fine.
 

Site & Scene News

Popular threads in this forum