I'm pretty sure it does. Part of how the SX chips work (if I'm not mistaken) is by injecting code into the NAND, and glitching the console so it will run the unsigned code. The injecting code into NAND part would probably fail with a blank NAND.
If you put the emmc on a nand board and program the partition and configure the emmc right using a unpatched erista. While having the OLED nand info on it. You can make it work. After that transplant it to the OLED. Use hekate to fix a few things. I did this for a mariko. With all the new improvement programs and stuff it’s probably easier and don’t need a unpatched. (Haven’t done a emmc upgrade in about 2 years now)
If you put the emmc on a nand board and program the partition and configure the emmc right using a unpatched erista. While having the OLED nand info on it. You can make it work. After that transplant it to the OLED. Use hekate to fix a few things. I did this for a mariko. With all the new improvement programs and stuff it’s probably easier and don’t need a unpatched. (Haven’t done a emmc upgrade in about 2 years now)
I've had an unpatched erista in the distant past, yes, I really regret selling it (even though I made a lot of money selling it). If I had it, I wouldn't even have opened this topic.
Flashing the user area (rawnand.bin) is easy with a sd card adaptor, but my headache is the boot area (boot0/1), i only need to understand how do this last.
All standard eMMCs should have the boot0 and boot1 partitions I believe, just they obviously wouldn't have Nintendo's bootloader. I can't imagine the modchips would care about the contents of those partitions, I'd think they'd just write their bct + payload to boot0 and do their thing (glitching the bootrom to think their bct is valid then letting the bootrom load the payload using the information provided in the bct as "normal").
But I have no experience with messing with any of this.
If I were doing it I'd see if any phone repair stores near me offer iPhone storage upgrades and if they do ask them if they would be willing to use their nand programmer to transfer the contents of my 64 gb module to the new one.
HWFLY-NX recognizes the situation and fixes it because I needed it on two OLED switches where I placed 256GB. If you have a full NAND backup, you can place an empty NAND and the firmware will write the necessary parts to your eMMC. You may contact me for details.
All standard eMMCs should have the boot0 and boot1 partitions I believe, just they obviously wouldn't have Nintendo's bootloader. I can't imagine the modchips would care about the contents of those partitions, I'd think they'd just write their bct + payload to boot0 and do their thing (glitching the bootrom to think their bct is valid then letting the bootrom load the payload using the information provided in the bct as "normal").
But I have no experience with messing with any of this.
Treading into dangerous territory here with the details, but the problem is to do with how the modchip's glitching mechanism distinguishes between failed attempts to glitch and correct ones. The mechanism relies on (valid/Nintendo signed) backup BCTs being present. Modchips detect when those valid ones get executed, and immediately reset the CPU and retry. Without valid ones in place, chances of successful glitches are minimal and it might take days before you ever get into hekate.
Treading into dangerous territory here with the details, but the problem is to do with how the modchip's glitching mechanism distinguishes between failed attempts to glitch and correct ones. The mechanism relies on (valid/Nintendo signed) backup BCTs being present. Modchips detect when those valid ones get executed, and immediately reset the CPU and retry. Without valid ones in place, chances of successful glitches are minimal and it might take days before you ever get into hekate.
i’m seeing V1 units with dock issues (for example) that work in handheld mode going for <$150. That’s only $20 more expensive than you were willing to pay for a sketchy lookin programmer.
i’m seeing V1 units with dock issues (for example) that work in handheld mode going for <$150. That’s only $20 more expensive than you were willing to pay for a sketchy lookin programmer.
Samsung
KLMEG8UCTA-B041 256gb new generation
KLMEG8UERM-C041 256gb old generation
KLMDG4UCTA-B041 128GB
KLMDG4UCTB-B041 128GB
Toshiba/Kioxia
THGAMRT0T43BAIR 128GB
FORESEE
FEMDNN256G-A3A44
Buy this emmc reader for switch. Klick me
Solder your original emmc to the daughter bord and dump all your partitions from the chip. Also boot0/1 partitions.
Do this under Ubuntu.
Then solder your new emmc to the daughter bord and copy all the partitions back.
Then solder the emmc to your OLED.
You can also use a old erista switch for it.
if you want to do this more often you should buy an emmc reader. Klick
But you need a special notebook SD card reader or the reader from the ali link above.
On xianyu/Idlefish you can find a usb version from a emmc reader for a good price. Klick
Or here Klick
btw.
Hekate restores the emmc backup whiteout problems to a bigger emmc.
yes that works,
In any case, it is important that the boot0/1 partition is described with the Nintendo bootloader. otherwise the chip cannot boot.
but please be careful when desoldering the emmc.