BTO, the priv.pem file is generated when I run the -r command. I tried just running the script without -r and as expected, everything had a fit and didn't activate. Following the instructions, I reloaded the 1.3.3.2 firmware and ran it again, and the same thing happened. I still am only getting 1 progress bar for reading the CFRAM and an assertion error instead of a second progress bar for applying CFRAM. This seems to be the only difference between the hack working and not working as I read through all the instructions and helpful comments. I tried disabling the firewall, upgrading to 1.3.3.0 and back down again, restarting the pc, and nothing solves the issue, it all comes back to this. The invalid licensing has left me with 5 more attempts remaining and I would rather not hit 0. I'm starting to feel like that one poor sap who's the only one this didn't work for. If you have any idea what the error could be please let me know, and thanks for your time.
This seems to be the only difference between the hack working and not working as I read through all the instructions and helpful comments
CORRECT...It is !
Basically, ... it's an ASSERTION ERROR
Let's just understand what that means, for a second
An Assertion error occurs when an ASSERTION is made and that Assertion Returns FALSE.
The purpose of the Assertion is to ensure that everything is ok, BEFORE ACTIVATION AND WRITING TO THE CFRAM, So... it's not damaging your scope, if anything, it's protecting it.
in the code there are only 5 Assertions that are made ever , they happen on the following lines...
91
122
127
143
158
In short and to keep it simple, it's checking a few things, the checksum, the priv.pem file and the hex key in your scope.
Basically and loosely stated, it's doing this.
1. let's examine the (len) THE LENGTH of the hex key in your scopes CFRAM
2. let's generate the priv.pem file
3. let's now compare the len THE LENGTH of the key in your priv.pem file
and len == len
which means.. the length of the key in your scope MUST EQUAL the length of the priv.pem hex key that will shortly OVERWRITE the CFRAM.
the basic idea here is... Let's not stuff things up so let's make sure that we match the length of the key with the correct length.
there's more to it, but in short it's saying... Let's not short change a digit in the key because that would result in really bad things for the CFRAM
HENCE WHY THE ASSERTION CHECK WAS PUT IN PLACE., Basically it's a good thing.
Here's what's ABOUT TO HAPPEN
it's generated the priv.pem
it's about to start writing to the CFRAM and replace the key in it for the new key
BUT IT WANTS TO MAKE ABSOLUTE CERTAIN before it does that everything is ok and cannot be any other way.
so since the Assertion returned FALSE, and Assertion Error is throw up and the entire script is HALTED.
so.. that's ok, Nothing bad has happnened to your scope yet.
The invalid licensing has left me with 5 more attempts remaining and I would rather not hit 0
DON'T EVEN WORRY ABOUT IT
You have 2 choices when it goes low, let's say to like 2 or something
1. Re install another Firmware version
2. Go back and activate it via the first activation method THE PATCH METHOD
then Drop down to a previous or higher firmware version.... it'll reset
dont worry about that
I'm starting to feel like that one poor sap who's the only one this didn't work for. If you have any idea what the error could be please let me know, and thanks for your time.
Not at all mate, don't feel that way. and.. i have every intention of getting you over the line.
This has only happened to 2 other people, Vs the .. i don't know 50 odd others that have contacted me and activate successfully
it has to do with the CFRAM in your particular scope, and ... it is weird, because i also have the MSO5072 and had no options installed and for me it worked fine
in a nutshell.... i would chance a guess that YOUR HEX KEY is not the same length as my HEX KEY was.
i also know that when you start with a ... say MSO5100 the Hex Key gets longer, that's what the version 3 is for , which is why it makes sense that that one would fail.
so... just focus on the first script
but since it failed, don't use it , don't try it again, ok
Now, Look I HAVE TO RUN OUT NOW, But i do have a few ideas
Now.... i'm confident we can fix this, if you don't give up. the other 2 guys that had this error, Gave Up and thanked me for my time
I would urge you not to do that. However i can't stop you if you don't want to continue. In their case
they got scared
they gave up
and they went back to the patch method
Ultimately, they got scared and paranoid thinking they would stuff up their scope. REMEMBER, An Assertion error is not damaging your scope or bricking it.
it protects it from that
Now, look
Do you want to jump on zoom or something , i think we can get this sorted quicker if we do it face to face.
i mean, i can give you instructions, but... it's kinda klunky and not efficient to do it that way.
Let me know
in the meantime i gotta do some work and i'll be back and i want to make some changes to the scrript, I've got a hunch that something may work, so all is not lost yet.. Keep your chin up and dont' lose hope ok.
I'll get you there
Basically we are 1 tiny step away from making it happen, we just need to know the length of your HEX key.
but we can't know that without pulling it apart and interrogating it. so what we do is we use the knowledge that DrMefist0 already put forward and we modify a few things (i won't go into detail here... it's boring)
but only to say... I can probably take a good guess based on what the script is asking for and asserting as to what happened
ALSO....
DID YOU INSTALL THE MODULES ?
STEP 13 of the pdf
HERE IS A LIST OF THE MODULES
argparse
base64
binascii
os.path
re
socket
struct
time
zlib
requests
tqdm
sha256
tabulate
xxtea
ecdsa
INSTALL THEM 1 BY 1 LIKE THIS
python -m pip install PACKAGE NAME HERE
so first CHECK THE LIST
pip install
then
python -m pip install argparse
and you'll get something like this
efaulting to user installation because normal site-packages is not writeable
Collecting argparse
Downloading argparse-1.4.0-py2.py3-none-any.whl.metadata (2.8 kB)
Downloading argparse-1.4.0-py2.py3-none-any.whl (23 kB)
Installing collected packages: argparse
Successfully installed argparse-1.4.0
NOW REPEAT THAT FOR ALL THE OTHER MODULES, if for nothing else but to upgrade the modules to the latest version.
if the modules are problematic it could spit up an Assertion Error.
I ALSO WANT YOU TO TELL ME IF THIS HAPPENS AT ANY POINT
WARNING: The script tabulate is installed in '/var/data/python/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
So you check the modules
i have to run out
when i come back i'll have a look at the script
and... let me know if we can catch up on zoom
let's do that for now