Hacking Hekate Ipl

  • Thread starter Thread starter Stoned
  • Start date Start date
  • Views Views 80,041
  • Replies Replies 200
  • Likes Likes 16

Attachments

  • 9BC113F2-01D0-4FF5-83FB-FC02DD3AEB7F.jpeg
    9BC113F2-01D0-4FF5-83FB-FC02DD3AEB7F.jpeg
    1.7 MB · Views: 522
No. if they were unreadable the dump would have failed. They were able to be read on the 2nd try which is why you only see their address once. The eMMC probably just gets tired and fails sometimes :shrug:
 
@rajkosto Thanks for your answer and sorry for my OS, i just need it to work.
And off course thanks for you work.

-- edit--

Edited the file, now it worked fine ... my OS isn't that bad ;)
 
Last edited by _n3o_,
jakkal doesn't know that my fork splits the USER partition into 2GB chunks, its not failing because of output filesize limits at all...
also, the progress bar overflows and starts back at 0% after a while, just wait until it prints Done. before closing it and you should get all the parts.

Heya, so I used your fork and everything dumper perfectly! I'm running the bash script to make the raw NAND file but it looks like it can't find gpt_prefix.bin. Any idea where I would get that? I imagine the original Hekate? Thanks for your hard work!
 
read the 2nd line of the pastebin/sh file for a hint

Unrelated: formatting your sdcard partition as exFAT with 128KB cluster size makes dumping way faster. My latest fork binary release is at https://github.com/rajkosto/hekate/releases/tag/rel_v3 and seems to be the most reliable of the bunch
 
Last edited by rajkosto,
How do you run it? What error does it give you? You should be able to just simply run it from the pegaswitch in any form.
(And I don't have it forked, because you just edit 4 slashes to get a full dump.)
I'd advise in splitting the dump in half. Pegaswitch cant handle that large of a dump all at once. Just edit 2 dump files and run them separately. Leave pega after the first and load back up. Make sure your terminal is stretched out and you can see at the debugging end to make sure it dumped. (It should give you two long numbers that are equal) I cant remember exactly though what it says. It will take about an hour all together to dump.
 
I'd advise in splitting the dump in half. Pegaswitch cant handle that large of a dump all at once. Just edit 2 dump files and run them separately. Leave pega after the first and load back up. Make sure your terminal is stretched out and you can see at the debugging end to make sure it dumped. (It should give you two long numbers that are equal) I cant remember exactly though what it says. It will take about an hour all together to dump.
i already dumped all at once and merged them using cmd is there anyway to make sure its a valid not corrupted dump?
btw its "29.1 GB (31,268,536,320 bytes)"
 
The size in windows file properties should be exactly 29,1 GB (31.268.536.320 bytes)
Linux shows it as 31.3GB, still 31,268,536,320 bytes though so everything is good. I wonder why windows shows it as 29.1GB (not that it really matters).
 
Linux shows it as 31.3GB, still 31,268,536,320 bytes though so everything is good. I wonder why windows shows it as 29.1GB (not that it really matters).

Hm i never knew linux shows it like that. I do know in windows 1 mb = 1024 bytes. So 31.268.536.320 bytes = 29,121 gb
 

Site & Scene News

Popular threads in this forum