Installing NSP with DBI : spinning wheel on home or corrupted game

[OuahOuah]

Hello.

I got a 16.x Switch with ATMO 15.2. + sigpatches.
I tried to install a NSP game with DBI and MTP transfer but at each try, eevn if DBI is ok, on home, I only have a little spinning wheel instead of the game.

Tried anothe rversion to test and the game icon is ok but the Switch tells me "Corrupted data".

Did I miss something on hack part ?

 

[Shadow#1]

Hello.

I got a 16.x Switch with ATMO 15.2. + sigpatches.
I tried to install a NSP game with DBI and MTP transfer but at each try, eevn if DBI is ok, on home, I only have a little spinning wheel instead of the game.

Tried anothe rversion to test and the game icon is ok but the Switch tells me "Corrupted data".

Did I miss something on hack part ?

Update your sigpatches

 

[DarkainX]

i had this the same. My cause was using de Hekate bootloader, and not the fusee one.

Can you try this out?

 

[OuahOuah]

i had this the same. My cause was using de Hekate bootloader, and not the fusee one.

Can you try this out?

How do I change from booting with hekae to booting with fusee ?

 

[Shadow#1]

How do I change from booting with hekae to booting with fusee ?

Inject fusee instead of hekate

 

[OuahOuah]

Ok, will look at this, as I inject Hekate with a tiny tool from Internet (ns-atmosphere).

 

[Rockfello]

Ok, will look at this, as I inject Hekate with a tiny tool from Internet (ns-atmosphere).

O guess you’ll have to change the file of the dongle and place the one for fusee instead of hekate.


Sent from my iPhone using Tapatalk

 

[OuahOuah]

Ok, seems solved : I injected fusee with tegrarcm gui in Windows.
Then installed with DBI and all ok.

Strange that it works better than launching hekate then fusse (cfw)...

Thanks all help

 

[Shadow#1]

Ok, seems solved : I injected fusee with tegrarcm gui in Windows.
Then installed with DBI and all ok.

Strange that it works better than launching hekate then fusse (cfw)...

Thanks all help

Because of your hekate_ipl.ini

 

[OuahOuah]

What can I put in this ini to boot correctly ?
When in hekate, I have three choices :
- boot in ofw+sysnand
- boot with cfw+sysnand
- booy with cfw+emummc (I always choose this). I though this one was fusee launching...

 

[alantgw]

Because of your hekate_ipl.ini

May you explain more on this?
Got the same problem, resolved with using fusee instead of hekate as well.

 

[The Real Jdbye]

What can I put in this ini to boot correctly ?
When in hekate, I have three choices :
- boot in ofw+sysnand
- boot with cfw+sysnand
- booy with cfw+emummc (I always choose this). I though this one was fusee launching...

Put fusee.bin somewhere on SD. Remove fss0= line and replace with payload= (and the path to fusee.bin)
You can't choose between sys and emu anymore, Fusee will always follow whatever is in emummc.ini. A lot of the settings in hekate_ipl.ini will have no effect when booting with fusee.bin.
Or do as stated below, to boot without fusee.bin.

May you explain more on this?
Got the same problem, resolved with using fusee instead of hekate as well.

Should work if you use the hekate_ipl.ini from the sigpatches, it should have the required kip1patch=nosigchk line. If not, add it to each CFW entry.

 

[alantgw]

Put fusee.bin somewhere on SD. Remove fss0= line and replace with payload= (and the path to fusee.bin)
You can't choose between sys and emu anymore, Fusee will always follow whatever is in emummc.ini. A lot of the settings in hekate_ipl.ini will have no effect when booting with fusee.bin.
Or do as stated below, to boot without fusee.bin.

Should work if you use the hekate_ipl.ini from the sigpatches, it should have the required kip1patch=nosigchk line. If not, add it to each CFW entry.

Thanks indeed it helps.
Omg it has been too long since I last updated Atmosphere and forgot the very basic stuff.
Thanks again!