Do you have a resized emummc?Minecraft Dungeons 2 doesn't launch successfully when using sys-patch 1.6.2.3; I've tested it on three different consoles running firmware 23.0.1 with the same result. Do you know if this is caused by sys-patch?
Do you have a resized emummc?Minecraft Dungeons 2 doesn't launch successfully when using sys-patch 1.6.2.3; I've tested it on three different consoles running firmware 23.0.1 with the same result. Do you know if this is caused by sys-patch?
You may try re-download and reinstalling the title, syspatch, atmosphere and hekate.Minecraft Dungeons 2 doesn't launch successfully when using sys-patch 1.6.2.3; I've tested it on three different consoles running firmware 23.0.1 with the same result. Do you know if this is caused by sys-patch?
sys-patch does not need the addition of sigpatches, you most likely are incorrectly adding sys-patch to your sd card and/or not rebooting after having added it.May be you add #7429 thread's sigpatch together with your system patch can help.
Without this, all titles were dead before with the latest system patch in v23.0.0+ firmware.
It's a good game supports multi-player in a Switch.
On the other hand, with the #7429 sigpatch and the latest system patch in v23.0.1 firmware,
The Battle Cats Unite! can not be started.
NetherSX2 titles with a icon, shortcut can not be created on home screen. There is only a white icon with spinning circle on the home screen. This can only use 3 out of 4 CPU cores if titles starts in the applet instead of game shortcut in homescreen.
no, because your previous post states this line of misinformation:There is no problem with the latest syspatch(without sigpatch) or titles before upgrading to v23.0.0+ FW.
System can reboots normally.
All titles can be launched.
May be this incidates sys-patch was correctly added?
May be you add #7429 thread's sigpatch together with your system patch can help.
Sorry for the delay; I work in technical support and waited for more consoles to arrive so I could test the error.it's not caused by sys-patch.
it most likely is a dynamic heap game,
but i cannot know, you have not provided a crash report or fatal report
your error has nothing to do with sys-patch, or sigpatches, or any of the projects i maintain.Sorry for the delay; I work in technical support and waited for more consoles to arrive so I could test the error.
- Minecraft Dungeons II installed without issues on Atmosphere 1.11.2 with sys-patch in its latest version, 1.6.2.3
Now I'll lay out my problem for you:
I updated to firmware 23.0.1 using Atmosphere 1.12.0, and when installing the base game of Minecraft Dungeons, an error screen appears with the following message:
bth: Thank you very much for the prompt response and the curious solution.0100000000000012 <-- bsdsocket sysmodule, network issue.
Atmosphère 1.12.0-master-28d6a2e11 <-- 28d6a2e was committed about an hour prior to the release...the release which does not support 23.0.1
Download BTH's fork. It shouldn't give you any issues. For giggles, I downloaded the game and installed it.
So it turns out I'm completely full of crap. I tried with DBI, Sphaira AND my own app. Every one gives a ticket install error. I turned off ticket installation on Sphaira and installed it anyway. Tried to launch it, and it tries to connect to the internet (which does not work for me at all since updating past 22.5.0; not just no Nintendo, no internet period). BUT: It's only that game. Everything else I throw at it installs and launches. Not sure if it's a bad rip that's floating around that we both somehow ended up with, or if it's a deeper issue (on my console at least, no internet is driving me bonkers, I can't even install stuff from my local Aerofoil setup because the wifi connection throws an error every time; tried 3 different networks and custom DNS, no dice).
EDIT: I'm assuming it's a personalized ticket probably based on a little bit of research, but I'm flying by the seat of my pants here. Going to try to NSC_Builder to convert to ticketless standard crypto, but I don't think that's going to work. I'll let you know.
that has nothing to do with sys-patch or sigpatches however.bth: Thank you very much for the prompt response and the curious solution.
I don't think the copy of the game currently circulating is corrupted, since I have a console running Atmosphere 1.11.2 and firmware 22.5.0, and Minecraft Dungeons II installs and runs correctly.
That’s why it caught my attention that this issue occurs when upgrading to 23.0.0 with Atmosphere 1.12.0.
all non-update tickets are personalized.EDIT: I'm assuming it's a personalized ticket probably based on a little bit of research, but I'm flying by the seat of my pants here. Going to try to NSC_Builder to convert to ticketless standard crypto, but I don't think that's going to work. I'll let you know.
IsGameCard: 0
distribution: type Download
contentType: Program
keyIndex: 0
size: 1661878272
titleId: 0100A7C01B792000
contentIndex: 0
sdkVersion: 22.2.0.0
KeyGeneration: 22
cryptoType2: 0
rightsId: 0100A7C01B7920000000000000000016
The only error I can turn up is from DBI, which says something about es sigpatches.that has nothing to do with sys-patch or sigpatches however.
sha256 verify the .nca's inside the .nsp or .xci or whatever you're using. Its the one reason why it'd fatal instantly
all non-update tickets are personalized.
All dumping tools convert it for the .tik file with certificate / install instructions to redirect it to the common ticket bin (non-personalized).
personalized in sense just means ticket inside of the private ticketbn signed.
it's more likely you people have a bad dump, as the crash log actually is obsering just the fatal:u response, and not what actually crashed it. Seems more probable it's NCM -> FS not liking the nca's (you have a whole lot of nca signature verification disable patches going on with sigpatches/sys-patch), and that also would prevent said checks from going "oh, this is corrupted".
edit: i went and just found a random dump:
Processing: v-minecraft_dungeons_ii.nsp
======================================================================
✗ Failed to extract CNMT: Invalid PFS0 header from <bytes input>: PFS0 header data too short: 0 < 16
sha256 seems correct
IsGameCard: 0
distribution: type Download
contentType: Program
keyIndex: 0
size: 1661878272
titleId: 0100A7C01B792000
contentIndex: 0
sdkVersion: 22.2.0.0
KeyGeneration: 22
cryptoType2: 0
rightsId: 0100A7C01B7920000000000000000016
And i happen to be more qualified to have an opinion.The only error I can turn up is from DBI, which says something about es sigpatches.
NCA:
Magic: NCA3
Fixed-Key Index: 0x0
Fixed-Key Signature: A4B7F25FD4C923A3843EF27488BAA452DCAE28E2D09F156AB548F3E6C27862B5
07BEE3D2C2F51E912E95FAFF940122DEB9C04FFAFF314456143BF32EB8F7C937
A0DB3E527DE80117EC06C5F2A356E5C6DD7BA36C193270541E6F44D468BD0FC6
778B7E62919C5F95239B724C3BDF81D59A2ADB0DB01B3B83C1AE7861989107BE
F9CD9BD489AAC0A336459B0B12665472CC92986CDEFC873CBCC87A1436F3CAEE
72A240C8DED3FA5F6B64F8DDF6DF56C29A08BFD65B32EB97744D1F2FF713F690
79119B58693719712700519FF753759857F7932A767C882A0F1B23E69769E815
563747C191DE3FAC97907A02E0FF14F16D477F7029CBEC73F67D725C1B22CEAA
NPDM Signature: B5960E9058D20A01A3C17D16F0036611BBD3D6CBFB4697FCD57F6571B3EBB076
D075D57C698F1A7CF4AA034F2BCC09FD4C10AAF26846FE9009E77F0066A1DD6A
821E9BDAEB21B13FCD56F4E2DCA93B2E4A0510D4E5B92A00F7055CD7EAFCC81B
A1442512B5A7F67AB45C3A51F30D14F9821E6EFFB075224F6324F4A9F0A8DD1C
5B416B17CED31F7C86AB80074C076BCD32C891046F2F04DEA92DCA6759EDF3F5
0E7C5B74542C16A24F5547C868573590C65C53D3E1FA35F3E580C5982FDDDA80
A590FFDA19213AD4C5B7D2D1E6AE8750516054593EEBEFFE89CE9B2B8AF21473
DA42E48703255EED386220EE3BC679A7F07A9C7FB9419269A4F63AE85ECDF946
Content Size: 0x0000630e4000
Title ID: 0100A7C01B792000
SDK Version: 22.2.0.0
Distribution type: Download
Content Type: Program
Master Key Revision: 0x15
Encryption Type: Titlekey crypto
Rights ID: 0100A7C01B7920000000000000000016
Sections:
Section 0 - Sparse section detected
SparseInfo:
sparseTabletOffset: 0x000000000000
sparseTableSize: 0x000000000000
sparseTableHeaderMagic: 0xBKTR
sparseTableHeaderVersion: 0x000000000001
sparseTableHeaderEntryCount: 0x000000000000
sparsePhysicalOffset: 0x0000630e4000
sparseGeneration: 0x000000000001
Offset: 0x0000f4e04000
Size: 0x0000059e0000
Partition Type: PFS0
Section CTR: 0000000100000000000000000f4e0400
Superblock Hash: BF0B9A0B7186DA9C4BE465C16397C4E1B6A0F5ABF499C332E7ECDC7D0B88B7E5
Hash Table:
Offset: 000000000000
Size: 00000000B3C0
Block Size: 0x10000
PFS0 Offset: 00000000C000
PFS0 Size: 0000059D241B
Section 1 - Sparse section detected
SparseInfo:
sparseTabletOffset: 0x0000630c0000
sparseTableSize: 0x000000008000
sparseTableHeaderMagic: 0xBKTR
sparseTableHeaderVersion: 0x000000000001
sparseTableHeaderEntryCount: 0x000000000322
sparsePhysicalOffset: 0x00000001c000
sparseGeneration: 0x000000000001
Offset: 0x00000001c000
Size: 0x0000f4de8000
Partition Type: RomFS
Section CTR: 00000002000000000000000000001c00
Superblock Hash: E1470611AE549BB1F647ECFB5D7813FAAD024532163DB0153CF5551AB7910274
Magic: IVFC
ID: 00020000
Level 0:
Data Offset: 0x000000000000
Data Size: 0x000000004000
Hash Block Size: 0x0000000e
Level 1:
Data Offset: 0x000000004000
Data Size: 0x000000004000
Hash Offset: 0x000000000000
Hash Block Size: 0x0000000e
Level 2:
Data Offset: 0x000000008000
Data Size: 0x000000004000
Hash Offset: 0x000000004000
Hash Block Size: 0x0000000e
Level 3:
Data Offset: 0x00000000c000
Data Size: 0x000000004000
Hash Offset: 0x000000008000
Hash Block Size: 0x0000000e
Level 4:
Data Offset: 0x000000010000
Data Size: 0x0000007a4000
Hash Offset: 0x00000000c000
Hash Block Size: 0x0000000e
Level 5:
Data Offset: 0x0000007b4000
Data Size: 0x0000f4633a94
Hash Offset: 0x000000010000
Hash Block Size: 0x0000000e
Section 2
Offset: 0x000000004000
Size: 0x000000018000
Partition Type: PFS0
Section CTR: 00000000000000000000000000000400
Superblock Hash: 5D02E6BBD346B5FCD4300763AF23CC1C1CE2C94AD7EDF8D52C75615083017755
Hash Table:
Offset: 000000000000
Size: 000000000240
Block Size: 0x1000
PFS0 Offset: 000000004000
PFS0 Size: 0000000117D4
requires nosigchk line in hekate_ipl.ini to use, requires official atmosphere release.It appears that the latest patches.ini (kip_patches) is not working when launching Atmosphère 1.12.0 via hekate v6.5.4.
exefs_patches and Sys-patch v1.6.2.3 are working without issues.
#FS 23.0.0-FAT32 - SDKVersion: 23.3.0.0
[FS:34383EE799926340]
.nosigchk=0:0x0278A8:0x4:00240036,1F2003D5
.nosigchk=0:0x07EEAC:0x4:01A80394,E0031F2A
#FS 23.0.0-EXFAT - SDKVersion: 23.3.0.0
[FS:FDAF163288E10805]
.nosigchk=0:0x0278B8:0x4:00240036,1F2003D5
.nosigchk=0:0x07EEBC:0x4:7DD40394,E0031F2A
#loader Atmosphere-1.12.0-master-28d6a2e11 (fw: 23.0.0)
[LOADER:92F34A795AA6F8CF]
.nosigchk=0:0x007F70:0x4:1F00016B,1F00006B
Thank you for the reply.requires nosigchk line in hekate_ipl.ini to use, requires official atmosphere release.
step 1 of solution is "no more lying"Just a quick question (I am still qualified to have those?):
If it's dumped incorrectly (as you say)
and we should "complain to mr dbi guy "why dont you support sparse nca?""
Why does it work on 22.5.0? Using DBI?
If it is, in fact, a borked dump, and it doesn't work because it's bad/broken/DBI doesn't do what it's supposed to do...
Why does it work?
I only ask because I'm not qualified to have an opinion, I was hoping you'd share yours?
You need the official AMS release as LDR patch in the patches.ini is only for that release.Thank you for the reply.
"requires official atmosphere release"
That was the answer. Files such as package3 had not been updated.
Sorry, still curious. Where, exactly, is the lie? (If I'm still lying, I can produce video for you as well).step 1 of solution is "no more lying"
i will not entertain any more hypotheticals from you on this subject. (enough time has been wasted into discovering sparse type ncas exist again, which only ever tinfoil has supported historically)
