Separate names with a comma.
CTCaer explained it: the emuMMC "driver" doesn't fully emulate all MMC operations. It can't work if the original driver isn't already loaded
From what I understand, this will downgrade your package2 (kernel + firm sysmodules) to fw 11.0 but will leave all titles on "SYSTEM" partition...
Maybe you're right, idk, only time will tell.
I have the same files. No clue.
TegraExplorer is basically dumping all ncas from Contents/Registered in SYSTEM FS. I've just checked on one of my switch on 12.0 and the total...
No, it should be around 316MB.
No it's not.
Reacher17's spoof has nothing to do with those BCPKG2 binaries (or "frankenbuild", as @Inaki calls them).
Lots of IPC changes in...
What are you trying to achieve ? To downgrade package2 ? Like in those binaries from shipengliang.com ?
What's the point of downgrading the kernel...
The spoof has nothing to do with official firmware. It'll always work on SX OS 3.1, no matter wich firmware is installed.
SX OS 3.1 has no...
There's always a boot sector in reserved sectors, that's how FAT works. You should try NxNandManager to re-format USER, it'll recreate boot & info...
From boot sector (SYSTEM & USER) :
512 bytes per sector
32 reserved sectors
32 sectors per cluster (cluster size: 16 KB)
Number of FAT : 2
I've just released: Release NxNandManager_v4.1.1 · eliboa/NxNandManager (github.com)
Yes, as long as you can still inject a payload (such as Hekate) to mount your sysnand on your computer
It should work yes, you'll have to restore BOOT0/1 too
You should first make a backup of your sysnand , it might be possible to unbrick it.
-1004 means invalid input/output file
Get the latest release for NxNandManager (your's too old) and name your prodinfo file exactly "PRODINFO.bin".
I'd say the usb-c cable is the problem. You should try with another one.
First you need to resize USER partition in your emuNAND. You can either use this python script or this program (windows)
Then you have to create a...
If you don't mind, and trust me enough, please DM me your prodinfo.bin and i'll look into.
NxNandManager displays "BAD CRYPTO" instead of device id when it cannot decrypt CAL0 (PRODINFO) using biskey0 =>...