Recent content by eliboa

  1. eliboa

    Hardware Dead eMMC restore options

    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
  2. eliboa

    Hacking Sx os 11.0.1 work round

    From what I understand, this will downgrade your package2 (kernel + firm sysmodules) to fw 11.0 but will leave all titles on "SYSTEM" partition unchanged (i.e 11.0.1). HOS gets the firmware version from SystemVersion title (0100000000000809). This title remains unchanged, which is why it'll...
  3. eliboa

    Hacking Hack SXOS

    Maybe you're right, idk, only time will tell.
  4. eliboa

    Hacking Hack SXOS

    I have the same files. No clue.
  5. eliboa

    Hacking Hack SXOS

    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 size is 316MB. Were there pre-existing files in your "tegraexplorer" folder before you dumped the new firmware ? You shoud only see these files in your...
  6. eliboa

    Hacking Hack SXOS

    No, it should be around 316MB.
  7. eliboa

    Hacking Hack SXOS

    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 sysmodules, according to SciresM. Downgrading package2 alone will not work this time, i'm afraid. Imho downgrading package2 is pointless anyway, it's not...
  8. eliboa

    Hacking Hack SXOS

    What are you trying to achieve ? To downgrade package2 ? Like in those binaries from shipengliang.com ? What's the point of downgrading the kernel or/and firm sysmodules ?
  9. eliboa

    Hacking Hack SXOS

    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 support for firmwares above 11.0.0, but that's another matter. If TX releases a new version of SX OS (very unlikely), they will try to prevent the spoof...
  10. eliboa

    Hacking Switch NAND layout ...

    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 sectors with original values (as much as possible). About your BitLocker tag problem, maybe there's a value somewhere in info sector that describes...
  11. eliboa

    Hacking Switch NAND layout ...

    From boot sector (SYSTEM & USER) : 512 bytes per sector 32 reserved sectors 32 sectors per cluster (cluster size: 16 KB) Number of FAT : 2
  12. eliboa

    Homebrew RELEASE NX Nand Manager

    I've just released: Release NxNandManager_v4.1.1 · eliboa/NxNandManager (github.com)
  13. eliboa

    Homebrew RELEASE NX Nand Manager

    Yes, as long as you can still inject a payload (such as Hekate) to mount your sysnand on your computer
  14. eliboa

    Homebrew RELEASE NX Nand Manager

    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.
General chit-chat
Help Users
    K3Nv2 @ K3Nv2: Spend 50 hours playing the game