Homebrew RELEASE JKSV (save manager) for Switch

  • Thread starter Thread starter JK_
  • Start date Start date
  • Views Views 202,802
  • Replies Replies 633
  • Likes Likes 27
Is it somehow ban safe to move saves files using this from the emuNand to the sysNand in ariplane mode? The saves are not hacked.
 
Is it somehow ban safe to move saves files using this from the emuNand to the sysNand in ariplane mode? The saves are not hacked.
I wouldn't be so bold as to say 100%, but I had hacked BotW saves on my sysnand, and never got banned.

EDIT: I should clarify that:

1) BotW is not an online game
2) I did this long before NSO was a thing, and I've never officially paid for NSO, so none of my save files have ever been uploaded to Nintendo's cloud.
 
Last edited by urherenow,
I wouldn't be so bold as to say 100%, but I had hacked BotW saves on my sysnand, and never got banned.
Cool, will try it later, I need to update both. I have saves all over the place cus i was lazy to switch back to the sysnand for some cartdrige.

Running CFW and Homebrew on the sysNand always has a risk but no one outside Nintendo really knows how much.
Tought as much.

Thanks.
 
  • Like
Reactions: Blythe93
2) I did this long before NSO was a thing, and I've never officially paid for NSO, so none of my save files have ever been uploaded to Nintendo's cloud.
I wouldn't worry about that. I've already uploaded saves immediately after I restored them and I haven't been banned. I've even had people tell me they expanded their Minecraft save archives to the maximum possible and uploaded it to NSO and haven't been banned. That should actually be a huge red flag and nothing AFAIK.

Edit: I should probably add that this was directly on my unbanned Switch. Not the main one I use which is banned. I have three Switches so no one gets confused.
 
@JK_ I'm unable to run JKSV after atmosphere got updated to support latest firmware, so it is just hanging at JKSV boot, even with latest JKSV version.

Checkpoint didn't work either.
 
@JK_ I'm unable to run JKSV after atmosphere got updated to support latest firmware, so it is just hanging at JKSV boot, even with latest JKSV version.

Checkpoint didn't work either.
@JeepX87 for JKSV work,open game with hold R,immediatly it opens HB Menu and open JKSV.
 
@JK_ I'm unable to run JKSV after atmosphere got updated to support latest firmware, so it is just hanging at JKSV boot, even with latest JKSV version.

Checkpoint didn't work either.
You're gonna have to give me some time to look into it. Sorry I haven't been too active lately guys. I just got finished dealing with a bad situation... Let's just say apparently I'm far from the ugliest guy on the face of the planet and I'm really good at guitar. Girls like that stuff a lot and it makes them go crazy... Don't ask how I know.
 
Nevermind.
Post automatically merged:

@JeepX87 for JKSV work,open game with hold R,immediatly it opens HB Menu and open JKSV.
You're gonna have to give me some time to look into it. Sorry I haven't been too active lately guys. I just got finished dealing with a bad situation... Let's just say apparently I'm far from the ugliest guy on the face of the planet and I'm really good at guitar. Girls like that stuff a lot and it makes them go crazy... Don't ask how I know.
I'm able to get JKSV loaded but require longer wait at startup screen.

Note: I always rely on R when open any homebrew apps for years, but longer startup screen is new issue that is very unusual because JKSV load quickly for years.
 
Last edited by Moe87,
  • Like
Reactions: Blythe93
You're gonna have to give me some time to look into it. Sorry I haven't been too active lately guys. I just got finished dealing with a bad situation... Let's just say apparently I'm far from the ugliest guy on the face of the planet and I'm really good at guitar. Girls like that stuff a lot and it makes them go crazy... Don't ask how I know.
take care of yourself, go and enjoy the life, is short, very short.
Post automatically merged:

By the way must have to do with the new memory restrictions on Atmosphère imposed by FW 20:

Basic support was added for 20.0.0.
  • The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
    • There shouldn't be anything user visible resulting from this, but it will be addressed in a future atmosphère update.
    • The same action item from 18.0.0 remains, and I believe in my heart of hearts that it will be addressed eventually. Someone has told me they're working on it.
    • There aren't (to my knowledge) outstanding 19.0.0 items any more.
  • Please note: As a result of changes made to nintendo's software in 20.0.0, there is roughly 10MB less memory available for custom system modules.
    • We can only steal a maximum of 14MB from the applet pool, down from 40MB.
    • To compensate for this, ams.mitm's heap usage has been reduced by 20MB.
      • To facilitate this, a new helper module (memlet) was added, so that memory may be temporarily stolen during the romfs building process.
      • Hopefully, this results in relatively little breakage, however it is possible that user mods which replace extremely large numbers of files in The Legend of Zelda: Tears of the Kingdom may no longer function.
        • If you are affected by this, you will see "Data abort (0x101)" when trying to launch the game with mods.
        • Please reach out to sciresm on discord if this occurs to share your error report binary. However, some issues may be impossible to fix.
        • I apologize sincerely if the issue is impossible to resolve, but I have been forced unavoidably to make compromises here, and I think this is the best balance to be struck.
I think the code will be needed to modified to use the new helper module memlet to ask for more memory..
 
I blame on Nintendo for mess but they don't take CFW in factor when they develop the update for Switch, lol.

It would be good neighbor if Nintendo make new update that is compatible with Atmosphere, so SciresM would like whoa, what's new Nintendo after curse gets lifted. GBATempers would demand Nintendo to do something like be friendly to emulators.

Joke aside, I need to make a clarification, the issue with Atmosphere is very slow to get loaded after atmosphere updated to support 20.0.0 and yes, I suspected that Nintendo changed the memory allotment that lead to have issues. I'm wonder about how many you have issues with slow startup? This issue is when run in full RAM, not applet mode and I never run homebrew programs in applet mode for many years.

Also, run JKSV or other programs in applet mode lead to crash that is not case with this issue that where homebrew program is slow to load.

It wasn't first time to see update broke the compatibility with JKSV and few other programs, so some members in here like Ely helped to fix the issue and later, JK developer updated JKSV to run smoothly, so that is not case with after 20.0.0 - just slow to load, that all.

take care of yourself, go and enjoy the life, is short, very short.
Post automatically merged:

By the way must have to do with the new memory restrictions on Atmosphère imposed by FW 20:

Basic support was added for 20.0.0.
  • The console should boot and atmosphère should be fully functional. However, not all modules have been fully updated to reflect the latest changes.
    • There shouldn't be anything user visible resulting from this, but it will be addressed in a future atmosphère update.
    • The same action item from 18.0.0 remains, and I believe in my heart of hearts that it will be addressed eventually. Someone has told me they're working on it.
    • There aren't (to my knowledge) outstanding 19.0.0 items any more.
  • Please note: As a result of changes made to nintendo's software in 20.0.0, there is roughly 10MB less memory available for custom system modules.
    • We can only steal a maximum of 14MB from the applet pool, down from 40MB.
    • To compensate for this, ams.mitm's heap usage has been reduced by 20MB.
      • To facilitate this, a new helper module (memlet) was added, so that memory may be temporarily stolen during the romfs building process.
      • Hopefully, this results in relatively little breakage, however it is possible that user mods which replace extremely large numbers of files in The Legend of Zelda: Tears of the Kingdom may no longer function.
        • If you are affected by this, you will see "Data abort (0x101)" when trying to launch the game with mods.
        • Please reach out to sciresm on discord if this occurs to share your error report binary. However, some issues may be impossible to fix.
        • I apologize sincerely if the issue is impossible to resolve, but I have been forced unavoidably to make compromises here, and I think this is the best balance to be struck.
I think the code will be needed to modified to use the new helper module memlet to ask for more memory..
That what I suspected and before Atmosphere was updated, I was worried about compatibility issues like we had one before.

I'm gratefully that is not break and I can wait one minute to get JKSV loaded.

@JK_ Hey, that is not emergency and please take your time.
 
I blame on Nintendo for mess but they don't take CFW in factor when they develop the update for Switch, lol.

It would be good neighbor if Nintendo make new update that is compatible with Atmosphere, so SciresM would like whoa, what's new Nintendo after curse gets lifted. GBATempers would demand Nintendo to do something like be friendly to emulators.

Joke aside, I need to make a clarification, the issue with Atmosphere is very slow to get loaded after atmosphere updated to support 20.0.0 and yes, I suspected that Nintendo changed the memory allotment that lead to have issues. I'm wonder about how many you have issues with slow startup? This issue is when run in full RAM, not applet mode and I never run homebrew programs in applet mode for many years.

Also, run JKSV or other programs in applet mode lead to crash that is not case with this issue that where homebrew program is slow to load.

It wasn't first time to see update broke the compatibility with JKSV and few other programs, so some members in here like Ely helped to fix the issue and later, JK developer updated JKSV to run smoothly, so that is not case with after 20.0.0 - just slow to load, that all.


That what I suspected and before Atmosphere was updated, I was worried about compatibility issues like we had one before.

I'm gratefully that is not break and I can wait one minute to get JKSV loaded.

@JK_ Hey, that is not emergency and please take your time.
@JeepX87 ,JKSV i also have a slow loading in full ram mode,in applet mode the Switch crashes and i haven't updated yet because i'm waiting for the final release of Atmosphere as always.
 
@JeepX87 ,JKSV i also have a slow loading in full ram mode,in applet mode the Switch crashes and i haven't updated yet because i'm waiting for the final release of Atmosphere as always.
I see, JKSV was fast for me before 20.0.0 dropped.

I don't know about what happened and I tried troubleshoot like removed all of old files, but it didn't change the behavior. I was consider about deep clean with fresh atmosphere but I don't think that is worth the hassle after I had one before and it didn't improve at all.
 
I see, JKSV was fast for me before 20.0.0 dropped.

I don't know about what happened and I tried troubleshoot like removed all of old files, but it didn't change the behavior. I was consider about deep clean with fresh atmosphere but I don't think that is worth the hassle after I had one before and it didn't improve at all.
@JeepX87 on my Switch it has always been slow to load in full ram mode,the important thing is that it works.
 
new Firmware have a memory restriction. Atmosphère behave different to accommodate to that, affecting JKSV.
@impeeza i haven't updated to the latest firmware yet, because I'm waiting for the (Master)version of Atmosphere(i'm still on 1.8.0)and JKSV is slow to load in full ram mode.
 
  • Like
Reactions: impeeza

Site & Scene News

Popular threads in this forum