Hacking SWITCH NOOB PARADISE - Ask questions here

[Hayato213]

how can i install games greater than 4GB with a microsd card FAT32 formatted? No usb, wifi, ftp.
thanks

You just going have to split the file if it it is larger than 4GB if you don't want to install via usb method.

 

[blueflue]

You just going have to split the file if it it is larger than 4GB if you don't want to install via usb method.

yeah thats why i'm asking.
what tools do i need to use to split the xci file?
which installer does work with splitted xci files?

 

[Hayato213]

yeah thats why i'm asking.
what tools do i need to use to split the xci file?
which installer does work with splitted xci files?

You should be able to divide the XCI with a program called Dividensp, even though it is for NSP it should work for XCI, you can use like Awoo installer, but easiest would just to install NSP, as they are smaller than XCI, save yourself some space, you should really learn how to do usb install, no need to split the file in the first place even if you have an FAT32 sd card.

 

[blueflue]

You should be able to divide the XCI with a program called Dividensp, even though it is for NSP it should work for XCI, you can use like Awoo installer, but easiest would just to install NSP, as they are smaller than XCI, save yourself some space, you should really learn how to do usb install, no need to split the file in the first place even if you have an FAT32 sd card.

are you sure it works with awooinstaller? i have tried it out allready but keeps giving "Failed to install game.xci/nsp, std:bad_alloc". Same issue with Tinleaf.

i cant find "Dividensp". No sucess with XCI Cutter and splitNSP.py
cant use usb, ftp, wifi in this circumstance.

 

[Hayato213]

are you sure it works with awooinstaller? i have tried it out allready but keeps giving "Failed to install game.xci/nsp, std:bad_alloc". Same issue with Tinleaf.

i cant find "Dividensp". No sucess with XCI Cutter and splitNSP.py
cant use usb, ftp, wifi in this circumstance.

That what is says on the Awoo github it support XCI,
https://github.com/Huntereb/Awoo-Installer
https://www33.zippyshare.com/v/GYPFJfVg/file.html

 

[blueflue]

That what is says on the Awoo github it support XCI,
https://github.com/Huntereb/Awoo-Installer
https://www33.zippyshare.com/v/GYPFJfVg/file.html

dividensp doesnt work, gives out error that the nsp file allredy exists.

 

[BigOnYa]

but easiest would just to install NSP, as they are smaller than XCI, save yourself some space, you should really learn how to do usb install, no need to split the file in the first place even if you have an FAT32 sd card.

Agreed...

--------------------- MERGED ---------------------------

i cant find "Dividensp". No sucess with XCI Cutter and splitNSP.py
cant use usb, ftp, wifi in this circumstance.

Yea that is rough...makes since now why...

 

[Escape1975]

dividensp doesnt work, gives out error that the nsp file allredy exists.

try this one ...
https://github.com/Aionmagan/NSPsplitty

Or switch to exfat, works very well for me

 

[lucoia]

Hi, I'm on SX OS 3.1b with 10.2.0 Emunand and I accidentally updated a game that needs firmware 11.0.1 and it won't start asking for the update. Is there a way to skip the update check to play it without uninstalling/reinstalling it (without the update) ?

 

[BigOnYa]

Hi, I'm on SX OS 3.1b with 10.2.0 Emunand and I accidentally updated a game that needs firmware 11.0.1 and it won't start asking for the update. Is there a way to skip the update check to play it without uninstalling/reinstalling it (without the update) ?

You can use Goldleaf, reset launch ticket.
To delete Game update notices in Goldleaf: Inside goldleaf Goto "Manage console contents", then "SD card", then select your game, then base or dlc, then select "Reset Launch Version". You then can play game on any firmware version.
Goldleaf 0.9 dev - thanks Raugo
https://mega.nz/file/gUtwiKJA#xmUS0HG8a9qV40aKqomWhbZqqSGCSL9L57Z2NAs6HTw

 

[shinwg]

Since some is patched to play on XS os mariko modchip. Is better to wait to see team excuter will release update or should I just move on to atmosphere.

 

[BigOnYa]

Since some is patched to play on XS os mariko modchip. Is better to wait to see team excuter will release update or should I just move on to atmosphere.

As long as you can stay on 11.0, and games don't require firmware higher, I'd wait and see what happens. I think eventually a official release will come, someone will crack the code, or the homebrew community will create they're own fix. But I must say I do love Atmosphere so that's a good option either way.

 

[lucoia]

You can use Goldleaf, reset launch ticket.
To delete Game update notices in Goldleaf: Inside goldleaf Goto "Manage console contents", then "SD card", then select your game, then base or dlc, then select "Reset Launch Version". You then can play game on any firmware version.
Goldleaf 0.9 dev - thanks Raugo
https://mega.nz/file/gUtwiKJA#xmUS0HG8a9qV40aKqomWhbZqqSGCSL9L57Z2NAs6HTw

Thanks, "Reset Launch Version" didn't work, the game kept asking to be updated, but I used Goldleaf to uninstall the update and everything is fine one way or another.

 

[shinwg]

As long as you can stay on 11.0, and games don't require firmware higher, I'd wait and see what happens. I think eventually a official release will come, someone will crack the code, or the homebrew community will create they're own fix. But I must say I do love Atmosphere so that's a good option either way.

Thanks buddy have you try patched game do they run good?

 

[Escape1975]

Does anyone know the purpose of updater2p=1 setting?
Seems like it replaces reboot_payload.bin with a hekate.bin file, is that right?

 

[Draxzelex]

Thanks buddy have you try patched game do they run good?

As @BigOnYa stated, no games require firmware 11.0 let alone 11.0.1 so there is no need to patch games to lower their firmware requirement. Games that you can patch their firmware requirement tend to run similar, if not identical, to their unpatched versions as long as the firmware is supported. That being said, there are some firmware requirements that you cannot patch out and demand that you do update your firmware. There is no telling when TX will drop an update, if ever, or if it will even support any newer firmware versions that may come out in the future. Your best bet is to just setup a dualboot with SX OS and Atmosphere.

Does anyone know the purpose of updater2p=1 setting?
Seems like it replaces reboot_payload.bin with a hekate.bin file, is that right?

The...what now? You will have to forgive me as I do not use any updater apps so you will have to be more specific. I also recommend you ask the question in that thread you just made in here.

 

[Escape1975]

The...what now? You will have to forgive me as I do not use any updater apps so you will have to be more specific. I also recommend you ask the question in that thread you just made in here.

The setting I mentioned is from hekate, in /bootloader/hekate_ipl.ini
(I don't use any updaters, I created my own SD from github pages)

 

[Draxzelex]

The setting I mentioned is from hekate, in /bootloader/hekate_ipl.ini
(I don't use any updaters, I created my own SD from github pages)

Well luckily the Hekate GitHub is very informative and answers your question for you. Quoted directly from the page itself (which I highly recommend you do if you have any questions about Hekate in general for the future):

0: Disable, 1: Force updates (if needed) the reboot2payload binary to be hekate.

 

[Escape1975]

Well luckily the Hekate GitHub is very informative and answers your question for you. Quoted directly from the page itself (which I highly recommend you do if you have any questions about Hekate in general for the future):

That's exactly the description I was confused about, but it seems to replace "reboot_payload.bin" so I think that answers my question, without that setting rebooting to payload doesn't get me back to Hekate from Atmos.

 

[Draxzelex]

That's exactly the description I was confused about, but it seems to replace "reboot_payload.bin" so I think that answers my question, without that setting rebooting to payload doesn't get me back to Hekate from Atmos.

That just seems like you reboot_to_payload.bin file is not Hekate. Vanilla Atmosphere certainly doesn't give you that nor does certain packages that don't bundle Hekate (which is becoming more common due to DZ).