Thanks for the new version, you outdid yourself ! 
Backup&verification took 89 mins on my samsung 256Gb Evo Plus ! :o
So I want to try a nand restore, as I said earlier in this thread, nx-dreport doesn't work for me on 3.0.1 and do have nand backups from before running homebrew (and encountering an error) and running SXOS with bad certs roms. (my switch never ever went online btw)
What file should I restore to eliminate the error and bad certs roms reports (I don't know where those would be stored on the emmc) ? would "SYSTEM" suffice ? or should I do a rawnand restore ? which option should I choose I the restore menu?
I know those backups are from a version of Hekate that didn't have verification but at least I managed to do the whole EXFat drivers installation with it, nand opened fine in hacdiskmount etc. so if anything goes wrong, I'll still have acess to RCM/Hekate to do the nand restore I just did and verified ok, right ?
thanks for your work and your help
Backup&verification took 89 mins on my samsung 256Gb Evo Plus ! :o
So I want to try a nand restore, as I said earlier in this thread, nx-dreport doesn't work for me on 3.0.1 and do have nand backups from before running homebrew (and encountering an error) and running SXOS with bad certs roms. (my switch never ever went online btw)
What file should I restore to eliminate the error and bad certs roms reports (I don't know where those would be stored on the emmc) ? would "SYSTEM" suffice ? or should I do a rawnand restore ? which option should I choose I the restore menu?
I know those backups are from a version of Hekate that didn't have verification but at least I managed to do the whole EXFat drivers installation with it, nand opened fine in hacdiskmount etc. so if anything goes wrong, I'll still have acess to RCM/Hekate to do the nand restore I just did and verified ok, right ?
thanks for your work and your help
Last edited by Azel,
SX OS supports sleep mode on 3.0. I asked CTCaer about sleep mode support for 3.X and he says he has to do some research before he can start working on a fix.no sleep on 3.0.0 yet
can someone help, im getting this error
it says sd card and eMMC data do not match verification failed
it says sd card and eMMC data do not match verification failed
Forgive my ignorance, but what is "Auto-Boot"?
The realist in me makes me think that it means that when you select "Launch Firmware" from the Hekate menu, it will wait an allotted time (as you can now set) and if nothing happens it will automatically load the default selection.
Optimistically, it makes it sound like it will simply automatically boot the firmware on entering RCM.
I presume the realistic approach is what it actually is. One can dream of the day you dont have to select any options on powering up (so long as autorcm is on). But it never hurts to ask?
Also if we had made a full backup nand with the previous release, does the new release imply that that backup is bad? or just not able to verify? I've gone through the upgrade process from 4.1.0 to 5 and I'd hate to have to downgrade just to pull the nand again (but hey, better safe than sorry).
The realist in me makes me think that it means that when you select "Launch Firmware" from the Hekate menu, it will wait an allotted time (as you can now set) and if nothing happens it will automatically load the default selection.
Optimistically, it makes it sound like it will simply automatically boot the firmware on entering RCM.
I presume the realistic approach is what it actually is. One can dream of the day you dont have to select any options on powering up (so long as autorcm is on). But it never hurts to ask?
Also if we had made a full backup nand with the previous release, does the new release imply that that backup is bad? or just not able to verify? I've gone through the upgrade process from 4.1.0 to 5 and I'd hate to have to downgrade just to pull the nand again (but hey, better safe than sorry).
Would that be an in-between answer? You'd still have to push the hekate payload down but then it just boots straight to the fw selected by auto boot? hmmm.. might be more than worth it then XD. I'll update it all eventually just want to make sure I do it right.
I havent used it myself yet, so I dont want to assume the wrong thing. But reading it made me think that when you turn the auto boot on, the payload will instantly just boot the OS and bypass the menu. But if you wanted to access the menu, I'd imagine you'd have to use your jig, press power and vol+ to put the Switch into RCM mode, then hold vol- before you plug the USB cable in to inject the payload.
I'm having issues creating a color correct bootlogo.bmp. I'm using GIMP -> export as bootlogo.BMP -> Advanced options 32 bit A8 R8 G8 B8. On booting hekate the screen has a terrible blue tint to it. I also tried the X8 R8 G8 B8 option which had a orange tint to it. I know the issue is the bmp I'm exporting because the bootlogo.bmp in tumGER's SDFilesSwitch works fine.
im doing it in parts and it keeps saying sd card and emmc data (@LBA 00002000>, do not match verification failed
Just tried again with a brand new Samsung 64 GB card and the full dump finishes but verification fails at 52%
[FatFS] Error: Read - Low level disk I/O!
Failed to read 8192 blocks (@LBA 01E98000), from sd card!
[FatFS] Error: Read - Low level disk I/O!
Failed to read 8192 blocks (@LBA 01E98000), from sd card!
Same here, the color on my custom splash is all messed up, no matter what settings I use in gimp
everything as far as I know goes to the root of your sd
It actually goes in SD:/Backup now
Last edited by wicksand420,
please?
--------------------- MERGED ---------------------------
i used version 2.3 to finish the backup, and it got past raw file 9
Similar threads
