yes, sorry for the delayed answer, I was busy.Oh my ... and that's known to be fixed in 3.1?
yes, sorry for the delayed answer, I was busy.Oh my ... and that's known to be fixed in 3.1?
Just a heads up, my understanding is that fs.mitm is not compatible with anything under 4.x, even though there are kernel patches applied for it. Something about differences between earlier and later firmware versions that aren't handled in the fs.mitm module itself.That's the kerel patch for fs.mitm (which is the true name of it).
And yes it should be.
Almost 2 hours? Oh my god. Did you have it plugged in.switch firmware 2.3.0
rawnand.bin
v3.0 --------> Failed to read 8192 blocks <@LBA XXXXXXX from sd card! Verification failed.. (time taken 71 minutes)
v3.1 --------> Finished and verified! (time taken 112 minutes)
thank you CTCaer!
Almost 2 hours? Oh my god. Did you have it plugged in.
Oh, well that's good to know. Thought it'd drain more. Hm.my sd card is old. (64gb adata)
i did not have my nintendo switch plugged in, the battery meter went from 95% down to %65.
what does means the error "SD card and data <ELBA 00002000> do not match"
after a backup of the nand ?
- Fix the verification code at last!
Another side-effect of using a 32bit ms timer (from the μs original one). Plus the additional fixes to variables that could not fit in u32 storage, makes the fix completely. Thanks to all the testers that helped to tackle these dreaded bugs.
Better redo that backup!
Well, if the problem is fs.kip, maybe using fs 5.x on a <4.X can make it work.Just a heads up, my understanding is that fs.mitm is not compatible with anything under 4.x, even though there are kernel patches applied for it. Something about differences between earlier and later firmware versions that aren't handled in the fs.mitm module itself.
Wish I had a source, but I read about it a while back, not exactly sure where.
Yeah. Only the hash process takes 45minutes. Also the maximum rate that eMMC and SD can have is low because the RAM is not initialized and BPMP is crap.Is the verification process on 3.1 supposed to take so long? It took less than an hour to make the actual backup but over 2 hours to verify it.
Not everyone was unlucky to reach that bug. And single file backup was working in v3.0 but it could fail because of the timing thing.@CTCaer - I managed to backup my NAND without hickups or errors using 3.0 and the checksums for the files are identical. Is there something in v3.1 that has changed dumpwise or can I trust that the backups I have are properly dumped and that only the verification code is fixed (which of I had no problem with and seeing the dumps are identical)?
...or could the dumps simply not match the NAND as the verification was wonky?
I think you read a description for another goddess, or you haven't read the whole article.@CTCaer just reacting to the Hekate desc. She is an underworld goddess, ruler of the ghosts, magic, necromancy etc. Governor of the Tartarus/Hell. So she is everything just not a protective and a blessing goddess i think based on this.
Anyway i know not you the one who made up this name.
i can use it with SD file v5 ???
Looking forward to thisThis is the next step.
Better utilization of the Security engine and sleep mode re.
If it's like other security engines, I can probably use it as memcpy to save some hundreds of milliseconds here and there.Looking forward to this
what do you mean by better utilization of security engine ? ^^