No you don't need them.
You need BOOT0/1 and the rawnand.
The SYSTEM and USER are included in the rawnand.bin
You need BOOT0/1 and the rawnand.
The SYSTEM and USER are included in the rawnand.bin
Thank you I have modded systems since I can remember & know the more info I can gather the better off I am. Now my brothers NAND won't rip and gets 3 errors every time. error reading 512 blocks @ LBA 0316D200 (try 1) & 0316D400 & 316D600 mine is A samsung 64GB U3 that works fine & his is A sandisk 64GB U1 both formatted ExFat. I'll give mine A shot after I wipe it. Would it matter if I put mine directly in his with my data on it or should I wipe it first after I back it up.
You can use your sd card on his without wiping it. But first backup your stuff. The dump files will get overwritten.
The important now:
The errors you are reffering to have nothing to do with sd card.
It's about reading from eMMC.
The current code tries to read 10 times for each failing 512byte sector before failing.
If it continues, the dump is OK.
So what's the case?
It shows
error reading 512 blocks @ LBA 0316D200 (try 1)
error reading 512 blocks @ LBA 0316D400 (try 1)
error reading 512 blocks @ LBA 0316D600 (try 1)
And continues and finishes the dump
or
it shows a try 10 and then the dumping cuts off?
PS: I will add messages to inform user when the dumping fails in error cases like these in the next release.
The important now:
The errors you are reffering to have nothing to do with sd card.
It's about reading from eMMC.
The current code tries to read 10 times for each failing 512byte sector before failing.
If it continues, the dump is OK.
So what's the case?
It shows
error reading 512 blocks @ LBA 0316D200 (try 1)
error reading 512 blocks @ LBA 0316D400 (try 1)
error reading 512 blocks @ LBA 0316D600 (try 1)
And continues and finishes the dump
or
it shows a try 10 and then the dumping cuts off?
PS: I will add messages to inform user when the dumping fails in error cases like these in the next release.
It always finishes and says try 1 on all 3..Happened all 3 times I tried it. And for some reason his dumps come out segmented as if he doesn't have enough space (might not actually but it's close) and for some reason one of the sections is very small compared to the rest (other than the final section/piece) maybe section 12 or so i'll have to check tomorrow which one. But i'll free up some space and give it another go with the stuff u told me.
Only 1 try, means that the 2nd try succeeded.
It is strange though that the 12th part (which includes the LBA sectors 0x316D200-600) finishes with smaller size. It should be exactly 2,147,483,648 Bytes.
The code does not dictate sth like this, except if I'm missing sth..
The partial dump only starts if you have a lower space available or FAT32.
When it starts, it shows the available free space VS the dump space needed, in MiB.
OK, now with the release of hekateipl for 5.0.x I gotta ask...
Is this payload compatible with 5.0.x firmwares? I've read good 4 pages of thread and didn't see anything about compatibility, sorry if I missed anything.
Is this payload compatible with 5.0.x firmwares? I've read good 4 pages of thread and didn't see anything about compatibility, sorry if I missed anything.
I know you said the errors wasn't because of the sd card but I used my samsung 64GB U3 card and my brothers dump went through without errors. And it was A full dump not broken up..Right before that I tried his sandisk 64GB C10 A1 sd card (thought it was U1 but it wasn't) & that didn't work...part 13 was really small compared to the rest even though it was an empty card when I tried it no full dump for some reason. Both formatted to Fat32. My bad...Just realized I might not even be using your hekate release....so take what I said with A grain of salt.
Last edited by link42586,
It should. But it probably can't launch HB Menu.
I haven't tried Jan4V's sd files yet, not launching to Switch OS though.
The hekateipl for 5.0.x has some extra security monitor patches that I think they patch Header signature, Version and Sections SHA2 for Package 2 (to be able to run a modified one?).
Last edited by CTCaer,
Hey, just posting to say thanks since I just used this to do a raw full nand backup. It took about an hour or so and I used a 64GB sandisk sdxc card formatted in FAT32 and this is what it looked like after I removed it from the Switch and put it on my PC:
I then used the batch file to put them together.
I then used the batch file to put them together.
Last edited by ThirdEyeCx,
@CTCaer I am having the same problem as @link42586 I try to dump my nand and get to about 90% and get an error, I have a usa console and it is on 5.0.2, my sd card is a 64GB sandisc.
@wicksand420 and @link42586
There is a trick that you can do:
First of all 90% should be the 12th part also. If another one except the last one is less than 2GB use this number in the following instead:
Move the successful files till the problematic one.
Create a file called partial.idx
With a hex editor, insert the part you want to continue from in HEX.
If it's the 12th, you must write 0C, which is 12 in HEX.
Go do the dump again and it will resume at 12th part.
@wicksand420
The above procedure is only if the card is FAT32 or the available free space is less than 31,268,536,320.
By the way I think I found why it does that and I will release a new version.
Be a little patient though, because my new release will have many changes and I have to make sure they are OK for upstream merging.
There is a trick that you can do:
First of all 90% should be the 12th part also. If another one except the last one is less than 2GB use this number in the following instead:
Move the successful files till the problematic one.
Create a file called partial.idx
With a hex editor, insert the part you want to continue from in HEX.
If it's the 12th, you must write 0C, which is 12 in HEX.
Go do the dump again and it will resume at 12th part.
@wicksand420
The above procedure is only if the card is FAT32 or the available free space is less than 31,268,536,320.
By the way I think I found why it does that and I will release a new version.
Be a little patient though, because my new release will have many changes and I have to make sure they are OK for upstream merging.
I switched to my samsung U3 sd card not my brothers sandisk card and it worked on both of our systems. Now I got both full dumps. So all good here but nice to know in the future.
Great work! Could you if you have time try to add your SD card patch (Samsung SDHC) https://gbatemp.net/threads/hekate-ipl-4-x-hbl-on-4-x.503471/ on this version ? Since it doesent support SDHC Cards and you found a workaround. Maybe you can apply the same code to that?
Best Regards
All my changes are upstreamed to main nwert/hekate repo. He can just cherry pick the commits to his release.
But don't worry, my new version will have 4.xx/5.xx support.
New version v1.3 released
Adds support for 4.xx/5.xx firmware launching and many other fixes/features.
Check OP for change log and download link.
Adds support for 4.xx/5.xx firmware launching and many other fixes/features.
Check OP for change log and download link.
Similar threads
