Quote:
Originally Posted by pikcachu
ah... you guys are awesome.... ya for some reason it doesn't work in the UI but it works if you call nbt.exe with the params....i generated the code that way... but was wondering why the UI wasn't doing it
wonder why esys does that thing with the spaces....
|
So, you're good now, right?
Humm, questions:
1. When you read the FSC via E-Sys, it appears it's already in binary form (not base64 encoded), correct?
2. You are able to manually generate the correct short code with the original FSC extracted from the car via E-Sys, right?
If both are yes, then E-Sys is extracting the correct FSC file.
It looks like Aritaurus had you base64 encode the FSC to make the GUI happy and that encoded FSC is what is bad.
If so, I wonder if the issue is that somewhere along the way, the base64 encoding step somehow messed the file up and that E-Sys is working correctly.
The SWID reader technique reads the FSC and base64 encodes it automatically, so that step is skipped when generating the short code.