New
#280
v5.7 uses different crypto key
edit > adds a second decryption key
v5.7 uses different crypto key
edit > adds a second decryption key
Hi guys
If you want to take a risk try using the leaked 10159 ISO (WD) -- works fine --available from usual places.
cheers
jimbo
Tested a few of Wzor's Twitter ESD and ISO mentions. At least one of the ESD didnt have the correct SHA1. You cant even tell for the ISO, naturally.
I recommend you get the ESD, check the SHA1, if correct, use this tutorial with the (soon to be updated) decrypter to make your own ISO.
OK geeks!
InformationThe download link in the tutorial now lets you select one of two tools, the ESDtoISO converter for Build 10130 and older, and the new ESDtoISO for build 10158 and later. Be sure to download the new tool if converting Build 10158 or later ESD files to ISO images!
The new tool is based on the Decrypter script version 5.7. All credits in the
ESDtoISO Read Me.rtf file.
Yes they work :)
The encryption keys used in the older tool were the issue; sometimes the tool / script worked with 10158 ESD file, sometimes not. If they worked and the ISO was created, the ISO is OK.
The new tool has updated encryption keys and works every time with Build 10158 and later ESD files.
depends on where you pulled the ESD from..
Not all ESD's are encrypted - ESD is also a compression format
If you do not receive a message of the decryption in process - then the ESD is not encrypted
the first script only needed a second crypto key added