where do i find the latest packer python script though? i have the scripts to unpack 1.3 and i can modify it but how do i package it back up into the boot.datTo those who want to crack SX. The best way i s to patch the license verification check in the loader ''tx" to always return true
https://gist.github.com/imPRAGMA/b135f59df43728b64662f466874836f4where do i find the latest packer python script though? i have the scripts to unpack 1.3 and i can modify it but how do i package it back up into the boot.dat
that is the old packer not the packer for 1.0 to 1.3, that will not check the sxos folder for all the files
that is the old packer not the packer for 1.0 to 1.3, that will not check the sxos folder for all the files
Thanks to everyone who uploaded V1.1! The scripts have been updated again to cover all versions.
— Mike Heskin (@hexkyz) July 13, 2018
again i already have that, it's not a packer
that is for creating a boot.dat that contains and boots hekatehttps://gist.github.com/CTCaer/13c02c05daec9e674ba00ce5ac35f5be try is to pack it back up
it's not the same, i have tried for example to replace it with the payload extracted from the original boot.dat and when you try to boot it all that comes up is can't find boot.dat or a black screen, i can't remember which it wasCant u edit the hekate_ctcear_3.2.bin bit in the script
As anyone done this yet and does it work cause i did buy an sx-os but i broke my switch it was on and dont wanna buy another one
yeah i had problems on windows with idaSeem to be having countless problems.loading the bins in Ida. Anyone else find a way to load them in Ida on Linux?
take the original data_80000000.bin or payload_80000000.bin (1.3) and goto this site https://md5file.com/calculator and drag it onto that to get the MD5 and then search stage2_40020000.bin for it, once found then alter the data_80000000.bin or payload_80000000.bin (1.3) and drag the altered file to the website to get the new MD5 and replace the one in stage2_40020000.bin with thatI can't find the SHA-256 checksum of original data in my stage2 file, I guess I must be doing something wrong...
I'm searching for 9C 2D 1D 41 67 84 EC C3 15 66 6A 93 7E 0B 9B 64 49 26 D7 AE AF D7 72 89 0F DA 96 C4 81 9C EA BC but the search says it doesn't exist...
How should I proceed ? Do I need to convert the SHA256 checksum to HEX ?
I was thinking to find the SHA 256.take the original data_80000000.bin or payload_80000000.bin (1.3) and goto this site https://md5file.com/calculator and drag it onto that to get the MD5 and then search stage2_40020000.bin for it, once found then alter the data_80000000.bin or payload_80000000.bin (1.3) and drag the altered file to the website to get the new MD5 and replace the one in stage2_40020000.bin with that
hexI was thinking to find the SHA 256.
Now I have the MD5 7769e1e2965fedabcfe8880991e9ae6a but I still can't find it inside stage2 file...
Should I find HEX bytes ? or will it be unicode text ?
it doesn't get that far with the info on OP, you just get the xecuter boot screen logo then it crashes so it doesn't generate the license-request.datWhat's happen when you put the generated
"licence.dat" on your Switch?
sorry my mistake it is the SHA-256 you copy from the site and look for XDI was thinking to find the SHA 256.
Now I have the MD5 7769e1e2965fedabcfe8880991e9ae6a but I still can't find it inside stage2 file...
Should I find HEX bytes ? or will it be unicode text ?
on your hex editor pick search, goto and enter 040A0 and on that line go across to 0C (the numbers across the top) and highlight everything upto 041A0 (0B) and look at the length it should say 100 and if you copy that into a new hex file and paste it in and save it you will see the size of the bin is 256 bytes which is correct.In data.bin, Swap out the public key @ 0x00040A0 (0C) (size: 0x100)
anyone know how to do this step?