No. It fails reading the file so it set it back to all 0Looks like your prodinfo bins are after the serial number was wiped.
No. It fails reading the file so it set it back to all 0
I went through these steps, but when I try boot Stock SYS via hekate it simply reboots hekate. What should I do from here?That is what you can try, you need to see if using hekate stock boot option would allow you to boot into that old NAND even though you have higher fuse count, backup current NAND first.
I went through these steps, but when I try boot Stock SYS via hekate it simply reboots hekate. What should I do from here?
Theoretically yes if you somehow or accidentally go online when using CFW or homebrew. In your example, even if you don't load CFW or homebrew on sysMMC, if emuMMC touches the Internet, you risk the whole console being banned. So its not a matter of what you go online with, its a matter of what you don't go online with.Sorry, I feel like I'm still not understanding. Going online at all, even with a clean sysnand will cause me to get banned?
It seems as if your PRODINFO backups have wiped serial numbers.It's OK. I renamed it to both prodinfo_sysnand.bin & PRODINFO.bin non of them did worke.
Some people are purists and prefer not to compress backups so as to maintain the authenticity of the original file. .NSZ files are functionally similar to .NSP files anyways. Also, there is no such thing as a "personal lockpick key". The reason users are instructed to dump their keys using Lockpick is because Switch keys are copyrighted material so they cannot be legally distributed. Therefore users are instructed to just dump the keys directly from the console since that isn't illegal, or that would be the case if not for Nintendo's DMCA towards its GitHub repo. At any rate, all Switch keys are the same and shared across all consoles except the BIS keys.Is there ever a reason to keep NSPs if one never intends to use Yuzu? I have kept everything as a mix of NSP and NSZ. If I want to compress or uncompress should I use a public key or my personal lockpik key?
Okay, I see now! Thank you. Is there a way to completely prevent emuMMC from connecting to the internet ever? I still am planning to play online only when booting into stock sysmmc. I'm also getting conflicting answers on what guide to use. Should I be using rentry or switch.homebrew?Theoretically yes if you somehow or accidentally go online when using CFW or homebrew. In your example, even if you don't load CFW or homebrew on sysMMC, if emuMMC touches the Internet, you risk the whole console being banned. So its not a matter of what you go online with, its a matter of what you don't go online with.
like do not enter your wifi password to it?Is there a way to completely prevent emuMMC from connecting to the internet ever?
Not connecting to the internet has worked for me so far.
No cable, no Wifi.
Yes, I put it into the hekate.ini in the bootloader folder.You try?
[Stock SYS]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock_boot.bmp
like do not enter your wifi password to it?
Yes, I put it into the hekate.ini in the bootloader folder.
NSZ has a nice verify option that can check both nsp and nsz files, not to mention xci and xcz. Here's an example of output. If it doesn't tell you about any errors, you can assume your files are ok.What does CR-XX mean on a rom file?
Is there a program that can scan my PC library for bad files before I attempt to send them to my switch?
python3 ~/.local/bin/nsz -V ~/Documents/Switch_downloads
NSZ v4.4 ,;:;;,
;;;;;
.=', ;:;;:,
/_', "=. ';:;:;
@=:__, \,;:;:'
_(\.= ;:;;'
`"_( _/="`
`"'
[VERIFY NSP] Celeste [01002B30028F6800] [v589824].nsp
[ADDING] 01002b30028f68000000000000000004.tik 704 bytes to NSP
[ADDING] 01002b30028f68000000000000000004.cert 1792 bytes to NSP
[ADDING] d71d739bebef56f2864f4d5f888729e2.cnmt.nca 6144 bytes to NSP
[ADDING] c301ae31d489c62ca43b2e79c9d7f86b.nca 464099840 bytes to NSP
[VERIFIED] c301ae31d489c62ca43b2e79c9d7f86b.nca
[ADDING] 65c5fcc93e4599aee893e93e6d55a91c.nca 1010176 bytes to NSP
[VERIFIED] 65c5fcc93e4599aee893e93e6d55a91c.nca
[ADDING] 59de5d4af6b4a83190282e0a2d6f83e8.nca 109056 bytes to NSP
[VERIFIED] 59de5d4af6b4a83190282e0a2d6f83e8.nca
[PFS0 HEAD] c6bc98cbd4ab1d74de5629e0dd2cdd696f8f84c7bf4a284605989de4d49997d8
[PFS0 DATA] e4a8427d5ffeb05059a280116c49d0b1b266fce945c5634a5461c5cfc111ed8b
[VERIFY NSZ] Fuga Melodies of Steel [01000130120EE800][v786432].nsz
[ADDING] 9f7c2643f12fc6dcb96c1cfb0301e499.cnmt.nca 7168 bytes to NSP
[ADDING] 4cfd622efed5691e5a5a5bb7d7b4b361.nca 96252631 bytes to NSP
Decompress 100%|████████████████████████| 130/130 MiB [00:02<00:00, 85.84 MiB/s]
[VERIFIED] 4cfd622efed5691e5a5a5bb7d7b4b361.ncz
[ADDING] 66bf92d84871729c96c621068298e6fc.nca 1144832 bytes to NSP
[VERIFIED] 66bf92d84871729c96c621068298e6fc.nca
[ADDING] f4ef1083b4800afac1c054dd0ed7a3d5.nca 81920 bytes to NSP
[VERIFIED] f4ef1083b4800afac1c054dd0ed7a3d5.nca
[ADDING] f8154193e9efa7a351323cdefd564873.nca 163840 bytes to NSP
[VERIFIED] f8154193e9efa7a351323cdefd564873.nca
[ADDING] 01000130120ee800000000000000000b.tik 704 bytes to NSP
[ADDING] 01000130120ee800000000000000000b.cert 1792 bytes to NSP
[PFS0 HEAD] ae4ab87791b4f03baf42c8773fc7e19226f8682cbc8587e56bdaf03cc2994762
[PFS0 DATA] 0cdeb7c7d96a25040657f9188e93b405cafbf1a09c73598a72a610dea9c69c6f
Done!
You could use both, you know? There's absolutely no harm in reading several different guides. You'll see that some information gets repeated, some information is missing from one guide, but mentioned in another. Just get the best from what you read. Don't just blindly follow any guide, try to understand what you're gonna be doing.I'm also getting conflicting answers on what guide to use. Should I be using rentry or switch.homebrew?
Yeah, you're right. I just want to be 100% sure of what I'm doing, as this feels more complicated than when I softmodded my other systems.You could use both, you know? There's absolutely no harm in reading several different guides. You'll see that some information gets repeated, some information is missing from one guide, but mentioned in another. Just get the best from what you read. Don't just blindly follow any guide, try to understand what you're gonna be doing.
So I can't revert it then?If you try it, then it just means that even with hekate it doesn't like the low firmware high fuse count.
So I can't revert it then?
All right, thank you for all your helpIf you tried to boot into stock with that stock option and it still won't boot, then no you won't be able to go back to older firmware.