YesIs thta the payload : hekate-ipl_ctcaer_1.3 ?
Yes (read below).Ok thanks, 16Go is enough for a complete dump ?
ok !Yes (read below).
Complete dump is around 30GB. Partial dumping will kick in.
Read OP for how it works.
@whyyes @Justin20020
Please try the attached beta version.
Changes:
Partial dumping:
Makes sure that the partial.idx is created even when a fatal error occurs. (helps to continue from the last part when an error occurred).
Can now force partial dumping by creating "partial.idx" file and writing 0x00 into it, even if the sd card has enough space (and fs is exFAT).
Other:
Optimizations
Fatal errors abort immediately. (They don't ask if you want to ignore errors now. What's the point if you get a corrupt backup.)
The one by one after the 1st session, was a test I forgot to remove from this beta version.It went really good. It took me 2 attemps (I don't know why but it stopped after one part on another)
Got 14 Parts. These are 29,1 GB (31.276.926.928 Bytes). So I'm good to go.
Thank you for your support on this, @CTCaer
Hi, I use hekate - ipl (CTCaer mod v1.3) in order to make a "RAW eMMC Dump" I had no problem except that I only have 14 parts of the rawnand.bin file, is this normal ?
The one by one after the 1st session, was a test I forgot to remove from this beta version.
Not exactly.
31.268.536.320 is the correct size. For some reason you have 8.390.608 more, which is 8MB + 2000B.
Did you merge anything else there? I believe you attached BOOT0/BOOT1 and sth else there.
Check if you parts are 2.147.483.648 and the last one 1.203.765.248.
--------------------- MERGED ---------------------------
The parts are from 00 to 14. That's 15 parts.
Tried this one, for a first time dump. Samsung 32gb card formatted ExFAT. It got to somewhere around 60% (raw full dump) before splooging errors all over the screen, possibly the same as a previous poster described. Attaching screenshot.@whyyes @Justin20020
Please try the attached beta version.
Changes:
Partial dumping:
Makes sure that the partial.idx is created even when a fatal error occurs. (helps to continue from the last part when an error occurred).
Can now force partial dumping by creating "partial.idx" file and writing 0x00 into it, even if the sd card has enough space (and fs is exFAT).
Other:
Optimizations
Fatal errors abort immediately. (They don't ask if you want to ignore errors now. What's the point if you get a corrupt backup.)
This is a beta version, you should use 1.3. Or better yet, for the final v1.5.Tried this one, for a first time dump. Samsung 32gb card formatted ExFAT. It got to somewhere around 60% (raw full dump) before splooging errors all over the screen, possibly the same as a previous poster described. Attaching screenshot.
That other poster just said that it took them two tries, so I'll give it another go later when back home.
All the other dumping options I tried (everything besides USER) worked fine.
E: I ran the other options AFTER the failed dump, there was enough free space to start with for the full raw dump, card was empty and freshly formatted.
The one by one after the 1st session, was a test I forgot to remove from this beta version.
Not exactly.
31.268.536.320 is the correct size. For some reason you have 8.390.608 more, which is 8MB + 2000B.
Did you merge anything else there? I believe you attached BOOT0/BOOT1 and sth else there.
Check if you parts are 2.147.483.648 and the last one 1.203.765.248.
Yeah, that's exactly what I got. I wasn't making stuff up just for the heck of it.Tried this one, for a first time dump. Samsung 32gb card formatted ExFAT. It got to somewhere around 60% (raw full dump) before splooging errors all over the screen, possibly the same as a previous poster described. Attaching screenshot.
That other poster just said that it took them two tries, so I'll give it another go later when back home.
All the other dumping options I tried (everything besides USER) worked fine.
E: I ran the other options AFTER the failed dump, there was enough free space to start with for the full raw dump, card was empty and freshly formatted.
Yes. It is intended for hekate to work like, let's say, android bootloader/twrp recovery.worked perfectly for me last night
dumped on my 200gb sd
--------------------- MERGED ---------------------------
will there ever be an option to restore from backup?
Sorry about that, I was thinking only for partial dumping and ignored the other case.Yeah, that's exactly what I got. I wasn't making stuff up just for the heck of it.
@CTCaer just saw your edit about 1.5. Great work identifying the problem! In the meantime I'm still trying the beta. It kinda works now. It's slow but no more read errors. I do get an message about too little space on the card but since there actually is enough space I always just continue the dumping process. I did of course double check that there is enough space.
Please mate, don't be sorry. It's all good, I'm thankful for your patience.Yes. It is intended for hekate to work like, let's say, android bootloader/twrp recovery.
For now though, we don't touch at all the writing to eMMC, until everything is ready.
Sorry about that, I was thinking only for partial dumping and ignored the other case.
--------------
Btw, all 1.5 bugs are sanitized and I'm just waiting confirmation from @Pizzlewizzle and someone else with 1.0.0 that the CFW launch works for these versions.
Although, that might not be needed in the future, because naehrwert will try and make the SE patches uneeded for launching any firmware version when he finds some time.