toxic
23rd December 2003, 05:20 PM
Hi,
I read this post a while ago and dismissed it thinking that its obvious that the simlock program checks the code and write something into the device to unlock it....
http://forum.xda-developers.com/viewtopic.php?t=3932&highlight=simlock
But... after simlock validates the first time, does the device check the simlock area, or just accept the return code from simlock?
That post demonsrates that you can rename some file to simlock.exe and make it run. Could it be possible for this program to 'pretend' to exit like simlock, and so validate the first time round.
Has anyone dismantled simlock to see exactly what it does, or in fact if we could reverse engineer its code validation algorithm (which should be a one way hash if they are sensible!)
Toxic
I read this post a while ago and dismissed it thinking that its obvious that the simlock program checks the code and write something into the device to unlock it....
http://forum.xda-developers.com/viewtopic.php?t=3932&highlight=simlock
But... after simlock validates the first time, does the device check the simlock area, or just accept the return code from simlock?
That post demonsrates that you can rename some file to simlock.exe and make it run. Could it be possible for this program to 'pretend' to exit like simlock, and so validate the first time round.
Has anyone dismantled simlock to see exactly what it does, or in fact if we could reverse engineer its code validation algorithm (which should be a one way hash if they are sensible!)
Toxic