Homebrew RELEASE Somes usefull homebrew on NSP

[chronoss]

I suppose it's good.
what I thought I understood, only by reading switchbrew wiki, and additional information provided by users, was:
000, 001, 002 etc.. up to 0FF are fine to use, they are considered as additional / different title content, like if a title can have 00 to FF possible installable slots (game and dlc)
and I thought that based on that information you had issues with:
01000A0000000001.nsp
01000A0000000011.nsp
I though the console considered both nsp as the same titleID, installed in 2 slots (0x01 and 0x11). both considered as DLC and missing the main game (0x000) if we refer only to existing ID used by nintendo.

But you said you don't have any problem, and they are each seen as individual title.
So, I think nintendo is enforcing their titleID only to themselves (when choosing it) and the switch doesn't care what the titleID is ?

You have more experience than me, as I didn't test installing nsp yet. All I said so far is only based on what I found, not what I tested and trusted results.

Ok, thanks for all information...

 

[zerohealinzz]

Sorry to post again, but when importing a save file with the nsp forwarder to the game i get the error:

Checkpoint error number: 0000f601

- Failed to comit to save device.


It then will freeze up or give an error code (2011-0301)

Creating a backup save will result in nothing except a crash or freeze.

he original save file is fine though, and booting from the NRO alone works normally

(save file is corrupt) as of now. rip me lol

 

[chronoss]

Sorry to post again, but when importing a save file with the nsp forwarder to the game i get the error:

Checkpoint error number: 0000f601

- Failed to comit to save device.


It then will freeze up or give an error code (2011-0301)

Creating a backup save will result in nothing except a crash or freeze.

The original save file is fine though, and booting from the NRO alone works normally

Forwarder or Standalone ?

 

[zerohealinzz]

Forwarder or Standalone ?

As stated its the forwarder.

I spoke to soon though, the backup i tried to restore with forwarder now seems to fail even in the original nro, it wont load the save file anymore (RIP) lol.

Tested the NRO on itself with another backup and that works fine.

I guess checkpoint dont secretly made a backup of my backup? ripppp xD

 

[chronoss]

As stated its the forwarder.

I spoke to soon though, the backup i tried to restore with forwarder now seems to fail even in the original nro, it wont load the save file anymore (RIP) lol.

Tested the NRO on itself with another backup and that works fine.

I guess checkpoint dont secretly made a backup of my backup? ripppp xD

Sorry for your save, i will make some test when i get time...

 

[zerohealinzz]

Sorry for your save, i will make some test when i get time...

I guess it is what it is.

For what its worth i added my save file to this post, might give u some clue (or none) the file is basically 0 bytes.

the save file was made before, worked fine until NSP exported it to the game.

I never overwrite the file (seems like the nsp did).

Game was Pokemon Quest.

 

[chronoss]

@zerohealinzz : i tested both file and all work well, i can make a backup and restore without problem....
I can't tested your save because i haven't the game installed...

 

[zerohealinzz]

@zerohealinzz : i tested both file and all work well, i can make a backup and restore without problem....
I can't tested your save because i haven't the game installed...

the save is dead so dont bother haha.

Let me find an old backup from couple of weeks ago and i test doing restoring that one. i update this post with result

EDIT:

Sorry took a while to find emergency backups lol.

Either way:

Checkpoint_01000A0000000012.nsp

Sd/switch/checkpoint.nro

Same error i added two pics of the errors in question.

Restoring save + error = no corrupt save file at all.

Creating a new backup = succes message + freeze or error code depending on my switch mood lol.

After reboot the newly created save + old backup is available. but new the save file is 0 bytes/empty/corrupt.

to be safe i tried three sd cards (256, 128 and 64 GB) didnt change and after that a 16 GB fat32, no luck.

https://imgur.com/a/wJMTk9y (pics of errors if thats even useful for you )

 

[chronoss]

the save is dead so dont bother haha.

Let me find an old backup from couple of weeks ago and i test doing restoring that one. i update this post with result

EDIT:

Sorry took a while to find emergency backups lol.

Either way:

Checkpoint_01000A0000000012.nsp

Sd/switch/checkpoint.nro

Same error i added two pics of the errors in question.

Restoring save + error = no corrupt save file at all.

Creating a new backup = succes message + freeze or error code depending on my switch mood lol.

After reboot the newly created save + old backup is available. but new the save file is 0 bytes/empty/corrupt.

to be safe i tried three sd cards (256, 128 and 64 GB) didnt change and after that a 16 GB fat32, no luck.

https://imgur.com/a/wJMTk9y (pics of errors if thats even useful for you )

I think it's a fw version because, all work fine for me on my 6.0 ReiNX

 

[zerohealinzz]

I think it's a fw version because, all work fine for me on my 6.0 ReiNX

Well rip fair enough, lets hope it is

I found out my emergency save was from yesterday so im good actually, if i ever get the courage to update to 6.x i might update you. But i guess by that time you know already what the problem might be.

 

[Reecey]

@Cyan Don't share these, they use most of the switch's legal keys in the build process with nro2nsp I have already thought of this sharing nsp homebrew alongtime ago on gbatemp, you really should take them down now! gbatemp will feel the heat else. Share them through a private message if your going to do this or on discord

 

[chronoss]

@Cyan Don't share these, they use most of the switch's legal keys in the build process with nro2nsp I have already thought of this sharing nsp homebrew alongtime ago on gbatemp, you really should take them down now! gbatemp will feel the heat else. Share them through a private message if your going to do this or on discord

Keys are in the programm ?

 

[Reecey]

Keys are in the programm ?

Yeah, in the keys.dat file in the resources folder. But hay I say grab them while you can

 

[chronoss]

Yeah, in the keys.dat file in the resources folder. But hay I say grab them while you can

 

[Reecey]

Also a little word of advice, its up to you but I wouldn't put your username in the "Made by" box especially when your linking the homebrew nsp for others to use & install

 

[chronoss]

Also a little word of advice, its up to you but I wouldn't put your username in the "Made by" box especially when your linking the homebrew nsp for others to use & install

Ok thanks but no one would know that it was done with such a program if one does not say its name...

 

[DocKlokMan]

I suppose it's good.
what I thought I understood, only by reading switchbrew wiki, and additional information provided by users, was:
000, 001, 002 etc.. up to 0FF are fine to use, they are considered as additional / different title content, like if a title can have 00 to FF possible installable slots (game and dlc)
example :
0100000ABCDE0000 <- game A
0100000ABCDE0001 <- DLC1 of game A
0100000ABCDE0002 <- DLC2 of game A
0100000ABCDE0800 <- update of game A

and I thought that based on that information you had issues with:
01000A0000000001.nsp
01000A0000000011.nsp
I though the console considered both nsp as the same titleID, installed in 2 slots (0x01 and 0x11). both considered as DLC and missing the main game (0x000) if we refer only to existing ID used by nintendo.

But you said you don't have any problem, and they are each seen as individual title.
So, I think nintendo is enforcing their titleID only to themselves (when choosing it) and the switch doesn't care what the titleID is ?

You have more experience than me, as I didn't test installing nsp yet. All I said so far is only based on what I found, not what I tested and should not be seen as trusted results. I hope someone has a proper explanation of the Switch TitleID system so I can learn it.

Little correction here. DLC is 0x1000 greater than base Title ID. So in your examples they'd be:
0100000ABCDE0000 <- game A
0100000ABCDE1001 <- DLC1 of game A
0100000ABCDE1002 <- DLC2 of game A
0100000ABCDE0800 <- update of game A

 

[chronoss]

Little correction here. DLC is 0x1000 greater than base Title ID. So in your examples they'd be:
0100000ABCDE0000 <- game A
0100000ABCDE1001 <- DLC1 of game A
0100000ABCDE1002 <- DLC2 of game A
0100000ABCDE0800 <- update of game A

Thanks but if you make the nsp with this title ID "0100000ABCDE1001" or "0100000ABCDE0800", what will it do ?

 

[Reecey]

Thanks but if you make the nsp with this title ID "0100000ABCDE1001" or "0100000ABCDE0800", what will it do ?

It will just overwrite that id, nothing major will happen, it wont brick or anything like that. For example you have a homebrew nsp with an id>0100000ABCDE1001 and then you forget and do another with the same id in the future all it will do is just overwright that original nsp with the new one.

 

[chronoss]

It will just overwrite that id, nothing major will happen, it wont brick or anything like that. For example you have a homebrew nsp with an id>0100000ABCDE1001 and then you forget and do another with the same id in the future all it will do is just overwright that original nsp with the new one.

Ok good !