Develop Bugs

Time To Modify IIWPO Theft Control.

hey guyz..
the scene is set, dont want to tell anyone where it happened by whom and ofcourse who got robbed but here's the story.
User had an o2 Xda II, customized rom, with IIWPO Theft Control installed in the rom, so that means hard reset wont wipe IIWPO out of the pda.
Robber comes puts a knife on the user's throat takes away cash and the pda, user gives it happily thinking she will get a msg on the other number with all the info of sim changed.
4 days pass by no info come's and the pda is sold or forwarded to someone else or whatever. END OF STORY.
now how did the user not get a msg of the new sim info.
1. SIM WAS NOT CHANGED.
2.SIM CHANGED BUT NO CREDIT IN NEW SIM.
3.BATTERY TAKEN OUT PDA TOTALLY DEAD TILL NEW CUSTOMER GETS IT. ETC ETC.
WHAT CAN BE DONE.
ok guyz this is the part where i would like allll the geeks & gurus to put in some effort, i know it will be tough but i have a feeling its not impossible.
CAN UR,LL UPDATE IIWPO IN SUCH A WAY THAT WHEN WE ARE FEEDING OUR NAME AND OTHER INFO IT WILL ALSO ASK FOR A SECURITY PASS TO BE PUT IN, SO THAT WHEN ROBBER CHANGES SIM THE IIWPO RECOGNIZES THE SIM CHANGE AND LOCK'S THE PDA AND ASKS FOR THE PASS, AND WONT UNLOCK TILL PASS PROVIDED, REBOOT WONT HELP.
Now ofcourse the robber can be anyone, so the robber plans to hard reset and still the device would recognize the sim change and ask for pass now so annoyed he plans to flash the device and what happens after that all of us know.
To prevent this THE GEEKS & GURUS can just build a small security patch that can wont allow flashing of device till pass given, it would work like this, we flash our device for the first time install IIWPO and the NEW SECURITY PATCH (with passwords) device is robbed, robber changes the sim gets pass error he gets pissed and tries to flash the device and that clever software would not flash the device till pass provided, this would prove that all the efforts the robber made to steal the device are gone to waste.
And ofcourse someday someone might put in a sim with credit and we would get the info.
NOT FORGETTING CHARLES WARNER FOR THE GREAT WORK HE'S PUT IN FOR ALL xda-developers.com USERS and also giving the IIWPO to us for free, REALLY APPRECIATE YOUR WORK SIR !! THANKS ALOT.

no one interested in being secured ?

I think the IIWPO idea can definitely be improved, BUT: It will never protect you from being robbed.
The true advantage of IIWPO in its currect form is to be able to get track of the 'new' owner of a nicked device. In the end: someone will put in his/her sim and then its just bing!
All other enhancements will just make sure noone else gets to use the device. Sure an improvement, but less important to me: I just want my device back and get the thief nailed!

Interesting...
But I think you have misunderstood how IIWPO works.
IIWPO does not detect if someone changes the SIM card. It ONLY acts when the someone changes the Owner Information (Start/Settings/Owner Information), so no matter what SIM card there is, as long as it has credit it will send an SMS to the recipient's phone number. That's the beauty of it, that it silently sends the SMS with the 'new' users data so there is a slight chance of knowing who's the 'new' owner.
But! This is by no means fool proof. It's what they call 'protection by obscurity', so if a savvy robber knows how to reflash the device it will get away with it no matter what features we can integrate to IIWPO.
That's one of the cool new features of WM5.0, that we can at least know for sure that our data is SAFE by wiping the info remotely if necessary.
Just a thought.
Rayan

edsub said:
The true advantage of IIWPO in its currect form is to be able to get track of the 'new' owner of a nicked device.I just want my device back and get the thief nailed!
Click to expand...
Click to collapse
Rayan said:
so if a savvy robber knows how to reflash the device it will get away with it no matter what features we can integrate to IIWPO
Click to expand...
Click to collapse
ofcourse this is why we all love IIWPO cause it sends use a msg, and ofcourse even if someone was to modify IIWPO iam sure that this feature would'nt wipe out.god forbid you get robbed u get a msg frm the cell but you for some reason cant track the person or some other c#@p...and the pda is gone....WHY caz it only sends sms it does not block the screen....if you were to have a feature which would jam or freeze the pda on change of the name then the pda would be useless to the robber nothing much he could do....unless he knows how to flash it...now comes a part where we can do something about not flashin the device with out a pass....this would totally make the pda useless to the robber and would also keep sendin us msgs and secondly the robber maybe maybe next time might think twice before robbing a pda and might go for something else

How about a device that would be installed internally to the xda and if it is stolen and a different sim/different user info is entered and the person makes a call it fires a large captive bolt which nails the phone to the head of the user, it then adjusts itself to full volume with all lights flashing and announcing "This is a stolen phone...call an ambulance...or hearse".,

cruisin-thru said:
How about a device that would be installed internally to the xda and if it is stolen and a different sim/different user info is entered and the person makes a call it fires a large captive bolt which nails the phone to the head of the user, it then adjusts itself to full volume with all lights flashing and announcing "This is a stolen phone...call an ambulance...or hearse".,
Click to expand...
Click to collapse
tht would be great..... are u goood enough to build something like tht ?

Rayan said:
But I think you have misunderstood how IIWPO works.
Click to expand...
Click to collapse
I perfectly understands the IIWPO functionality. It was me who put together IIWPO for other devices than Wallaby.
Let me explain how my earlier post should be interpreted: Sure it is triggered by the change of owner info, but most thieves (or buyer from a stolen device) will put in another SIM (simply because they dont have the pin of the stolen sim or because the stolen sim is blocked by the network). Thus: As soon as the 'new' owner puts in a SIM AND he/she has changed the owner info (and every one does that!) the sms is sent.
Also: Eventually a thief might flash a device, but ost certain a thief (or buyer) starts it up to test whether its working or not.
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve

edsub said:
Rayan said:
But I think you have misunderstood how IIWPO works.
Click to expand...
Click to collapse
I perfectly understands the IIWPO functionality. It was me who put together IIWPO for other devices than Wallaby.
Let me explain how my earlier post should be interpreted: Sure it is triggered by the change of owner info, but most thieves (or buyer from a stolen device) will put in another SIM (simply because they dont have the pin of the stolen sim or because the stolen sim is blocked by the network). Thus: As soon as the 'new' owner puts in a SIM AND he/she has changed the owner info (and every one does that!) the sms is sent.
Also: Eventually a thief might flash a device, but ost certain a thief (or buyer) starts it up to test whether its working or not.
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve
Click to expand...
Click to collapse
Sorry edsub, I should have specified to whom I was refering to (zairyaab) when I wrote that comment.
Best regards,
Rayan

np m8

edsub said:
It was me who put together IIWPO for other devices than Wallaby.
Click to expand...
Click to collapse
Can you explain what should I change in the cab to make it work on other devices (Like ETen M500/Torq P100)?
edsub said:
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve.
Click to expand...
Click to collapse
Yeah, but still I would feel somewhat better if I can at least call the thief/buyer and shout some expletives if he/she refuses to cooperate!!! :twisted: :lol:
Best regards,
Rayan

i have my girlfriend's number as my report number.. what if were together and we got robbed both our phones are taken away.. a multiple report number would be a good addition to IIWPO

The changes I'd like to see done to IIWPO include:
a) not using "IIWPO" or 'xda-developer' in the registry (user customisable registry key)
b) user customisable executable file name (IIWPO_startup is like a dead giveaway)
c) not storing owner name & number 'in the clear' (a simple XOR to hide it would be just as effective)
d) a hash of the entire owner info page (not just the last name) so unit will resend an SMS if any info changes
e) a new sms is resent after a preset time (eg: every 24/48/120 hours for example), regardless if owner info has changed or not.
I also like the idea of multiple number reporting.
a,b,c) Considering the concept of IIWPO is 'security by obscurity'; it will help if one could hide it more effectively. (no one is going to bother too much about bluetooth.exe or msn_update.exe in the startup folder for example...)
d) Most people get their name right; then meddle with the other bits of information as time goes on - it'd be good to get 'updated' info as and when it happens.
e) Consider it a 'keep alive' thing, so we'll know the unit is still in use, and can continue to keep in touch with the new owner =) I've no moral issues burning up the credit of someone who refuses to give me back my property either. =P
If nothing else, we'd be able to know when the unit gets reflashed, and can quiety say goodbye to our unit after not hearing from it for a while... =(
Is IIWPO still being maintained by the author, or anyone on xda-developers? If not, is the source available? I might be interested in following up on it (time permitting...)
Edited to add: A really vicious version of the IIWPO would possibly send out:
a) phone numbers stored in the SIM card
b) phone numbers stored in the addres book
c) recently dialed/received phone numbers
d) recently sent/received SMS phone numbers
Not all in one go; but in bits and pieces (eg: every 20 startups; send phone numbers of last 5 SMSs sent/received + last 5 phone calls dialed/received).
That would allow us get in touch with his friends and would possibly aid in getting the unit returned (use your imagination... probably easier to get them tell you who/where he is, rather than to get them convince him to return it...)
Probably this would add too much bloat to IIWPO; but hey, could be useful... =P

WOW, ok.
First of all - I registered 2 this forum less than a week ago,
and great job for doing these kind of things.
second - where can i d/l the prog?
and last another idea: when some1 steals ur pda he's usually gonna sell it over. meaning he made his money.
HOWEVER - if even after a HR after changing sims (maybe even without) there will be a picture message saying:
"You cannot use this phone"
"This phone can only be used by me - *name*"
"However, Im willing to buy this phone back from you. call +......"
there wont be a place on the screen to enter the code.
however - the phones' user knows he can type his password and unlock the phone. you might even integrate a handwriting recognition programm for signature or somthing but that will be super hard, i know.
another option is that when seeing this message user has to touch 4 corners of the screen with the stylus in a specific order, then he'll have a please enter password screen.
any comment?
is it do-able?

http://wiki.xda-developers.com/index.php?pagename=IIWPO

Black rom 2.5 results in new device ID (for software activations)

Any one figured this out yet?
Basically the tomtom calculates the device code (I thought this was via imei)
Well since installing black 2 I can not longer use tomtom plus services (speed cams traffic e.t.c)
I can change the device code on there website once every 6 months BUT if the same thing happens with black 3 then It wont work, there is a similar thread I have replied to on the upgrades forum which may be a clue as they had the problem with CID unlocking, my device has had all that dont about 6 months ago many roms and "device names" later (one actual device) it now has it thinking its a new device.
I am guessing this is going to happen with a few other bits of software from what I have read in the searches (opera and a few other similar bits of software).
Why would this happen with these latest wm6 roms not previous wm6 roms.
My main worry is if this happens randomly with every new rom, and Im guessing this may not be isolated to this batch of roms.
Similar thread which may give a clue but thought this was more suited to the wm6 forum after I posted :/ lol
http://forum.xda-developers.com/showthread.php?t=284147
Thanks in advance

Start > Settings > System > About > Device ID

CUSTEL;1247299 said:
Start > Settings > System > About > Device ID
Click to expand...
Click to collapse
I'm pretty sure that isn't what he is referring to.
It's a unique string that identifies your device.
For example;
With AEButtons and WM5, I had a Device ID that started with D1 C3.... and then moving to WM6 it changed to something like C6 A2...
I was able to activate AEB just fine, it just shows that I have activated 2 devices at AEB's website activation page.

Karzi said:
Any one figured this out yet?
Basically the tomtom calculates the device code (I thought this was via imei)
Well since installing black 2 I can not longer use tomtom plus services (speed cams traffic e.t.c)
I can change the device code on there website once every 6 months BUT if the same thing happens with black 3 then It wont work, there is a similar thread I have replied to on the upgrades forum which may be a clue as they had the problem with CID unlocking, my device has had all that dont about 6 months ago many roms and "device names" later (one actual device) it now has it thinking its a new device.
I am guessing this is going to happen with a few other bits of software from what I have read in the searches (opera and a few other similar bits of software).
Why would this happen with these latest wm6 roms not previous wm6 roms.
My main worry is if this happens randomly with every new rom, and Im guessing this may not be isolated to this batch of roms.
Similar thread which may give a clue but thought this was more suited to the wm6 forum after I posted :/ lol
http://forum.xda-developers.com/showthread.php?t=284147
Thanks in advance
Click to expand...
Click to collapse
I opened a call at Tomtom for that. I have the same problem. I asked to have a solution of a code based on the hardware and not on the operating system.
The answer: impossible. I must indicate the link of new the ROM and they correct the code.… I did not test yet…

I've run into the same situation with TomTom. It's a bit of a pain. Still working through the issues with them.
Timothy

I think the API to get the device's IMEI got broken in the latest WM6 builds. I too have the TomTom license problem, and Opera Browser for Mobile is also complaining that the device ID has changed. Prior to upgrading WM6 (LVSW 20070423), Opera Browser would read the IMEI (device ID) correctly. After upgrading, it now reads a completely different number (not even remotely close, for one thing, it is two digits shorter). However, when I look at the IMEI shown in "Device Information", or #*06# from the phone dialpad, it is correct.
In both my cases (TomTom and Opera), I was quickly able to get new license keys from each, but it is still a pain.
WTF, M$ & HTC???
John

Same happened to me with the Hebrew add on. Strange.

Had the same wit Hebrew as well...

Yup, same problem here, I'm with Berdinkerdickle, there is a hex code that you can see with AEB Plus's registration screen that comes from the OS I guess. It changed from stock WM5 to Black 2.0 and now again with 2.5
Slingbox Mobile seems to use it internally to lock it to an individual device. The prog actually logs onto the sling site each time you use it and checks this number against the issued key code, this is independant of user inputted ID name like most progs. If there is a mismatch the program tells you that you have 30 days remaining and counts down till you enter a new code provided by Sling, which means an email conversation with them each time to get a new code.
AEB Plus as noted, shows you the internal code string and has you enter that string into their website to get an activation code. (I'm on my 3rd web re-activation and wondering if AEB has a max cut off number?)
I looked over the thread referenced on the first post and it mentions super CID, I've not done that to mine yet.
The device code is a hex string listed as 7 pairs of numbers in AEB Plus (xx xx xx xx xx xx xx) is this the CID code?? and if it is, is it linked to the OS, uniquely by device?? That doesn't make sense to me.

Same problem for me, with SlingPlayer and a few other applications. Ugh. Every time I put a new ROM on there, the device ID or whatever they're using changes. They must think I'm trying to equip an army with Slingplayer licenses.

jmat said:
Same problem for me, with SlingPlayer and a few other applications. Ugh. Every time I put a new ROM on there, the device ID or whatever they're using changes. They must think I'm trying to equip an army with Slingplayer licenses.
Click to expand...
Click to collapse
I had it with a few apps as well. With Slingbox they indicated that it's not a problem at all since once they issue a new code, the old one is invalidated. They don't really care.

never mind...

johnburn said:
I think the API to get the device's IMEI got broken in the latest WM6 builds. I too have the TomTom license problem, and Opera Browser for Mobile is also complaining that the device ID has changed. Prior to upgrading WM6 (LVSW 20070423), Opera Browser would read the IMEI (device ID) correctly. After upgrading, it now reads a completely different number (not even remotely close, for one thing, it is two digits shorter). However, when I look at the IMEI shown in "Device Information", or #*06# from the phone dialpad, it is correct.
In both my cases (TomTom and Opera), I was quickly able to get new license keys from each, but it is still a pain.
WTF, M$ & HTC???
John
Click to expand...
Click to collapse
The API isnt broken... works fine in Black 2.0, 2.5 and 3.0, as well as all of LSVW ROMS...

Skyscape
Same problem with
Skyscape applications (medical references)
http://www.skyscape.com

johnburn said:
I think the API to get the device's IMEI got broken in the latest WM6 builds. I too have the TomTom license problem, and Opera Browser for Mobile is also complaining that the device ID has changed.
Click to expand...
Click to collapse
The irony is that people who didn't pay for these applications have zero problems..
Copy protection doesn't hurt anyone but the legitimate people..
The worst part is, I can't even suggest that you (the legitimate purchaser) use the keygen floating around give yourself access to your product.. because that would cut you off from your online services..

icemantwilight said:
The irony is that people who didn't pay for these applications have zero problems..
Copy protection doesn't hurt anyone but the legitimate people..
Couldn't agree more!!
Click to expand...
Click to collapse

mrvanx;1248020 said:
never mind...
Click to expand...
Click to collapse
Sure, No Problem.
Yea, I wish we could delete our posts rather than
only being able to edit them.

Karzi said:
Any one figured this out yet?
Basically the tomtom calculates the device code (I thought this was via imei)
Well since installing black 2 I can not longer use tomtom plus services (speed cams traffic e.t.c)
I can change the device code on there website once every 6 months BUT if the same thing happens with black 3 then It wont work, there is a similar thread I have replied to on the upgrades forum which may be a clue as they had the problem with CID unlocking, my device has had all that dont about 6 months ago many roms and "device names" later (one actual device) it now has it thinking its a new device.
I am guessing this is going to happen with a few other bits of software from what I have read in the searches (opera and a few other similar bits of software).
Click to expand...
Click to collapse
Same problem with my TomTom, does the new Black 3.0.1 solve this issue?

Black 3.0.1 goes back to the same hardware ID that was around in Black 1.0 and Black 2.0. So.. I guess it's fixed? It seems like there was a build of WM6 out there that really screwed with things -- because all of the other ROM's had the same problem.

jmat said:
Black 3.0.1 goes back to the same hardware ID that was around in Black 1.0 and Black 2.0. So.. I guess it's fixed? It seems like there was a build of WM6 out there that really screwed with things -- because all of the other ROM's had the same problem.
Click to expand...
Click to collapse
I didn't check Black 1 or Black 2, was the ID the same as WM5 with these versions of WM6? It was only a fault in roms v2.5?

Device ID

Hi
I recently started flashing my tytn with your excellent roms but failed to write down my Device ID and know I'm having problems registering my touch-commander. I'm not clear about the concept of the Device ID!? Does the Device ID change everytime you flash? I hope I didnt overlook some stupid little detail but it shouldn't be that hard I don't want to buy a new license and I have tried The Cube but find it less responsive than touch-commander!

It's a user setting so if you did not right down the device id it will have probably changed to what ever was set as the default in the ROM you flashed. This is why if you have registered software your supposed to write it down and then you can set to to what it was before to avoid the problem you are having.
If you never changed it someone around here may know what the default is but they will need to know what carrier you purchased it through to determine this information or you can contact your carrier and they should know what it was.

How do you get around device id's being changed when changing rom?

I run a couple of bits of software on my phone which the licence is registered to the device id. When I change the rom on my phone the device id changes. Is there anyway I can stop the id changing? I have to contact my software provider each time to explain I have changed phones and can they supply a new licence on the new device id, I dont think they're going to keep doing this for free
Thanks.

A very good question!!

Unlocking NoDo with temp dev account - possible?

Hello,
a friend has a dev account and therefor he can unlock several wp7 phones when using his live id and adding my phone to dev phones. NoDo works too of course.
My thoughts are: if i update my phone he could add it as dev phone and the DeveloperUnlocked key would change from 0 (after NoDo update) to 1.
Next step would be that I change the reg keys (because of dev status i could use the reg editor) that have been the cause my HTC Mozart 7 got relocked when i connected to zune:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
And now i would change back to my live id and he would remove my phone from his dev phone list - would the DeveloperUnlocked key change to 0 again or won't it be possible because of the DeviceReg "hack" above?
I don't know what is causing the change from 1 to 0, is it just zune connect or does this change apply via Wifi/3G also? Are the two keys above still actual for NoDo?
It would help everyone who knows a person with dev account to get the NoDo unlocked

Right the person that i searching for.
How does the unlock of a second or third device work? Can the person with the other device we wont to unlock use my Live-ID without the use of my Id on his phone? I found nothing about this in the App-Hup.

not possible.
only the FIRST live ID can unlock a phone and you will be stuck with that account.
that mean that you can't use your own email account for online services and your friends email account is always in your phone.
to change that you would need to hardreset the phone and then the unlock is gone to.

Thanks for that information.

Ah right, i forgot that that the change of the FIRST live id needs a hardreset. Thanks for pointing that out.
I wondered WHY you have to hardreset your phone to change the main live id. Now i know why =)
To sum it up: dev account needs to put the matching live id as the FIRST on the phone, so you would need a hardreset to do that. And another hardreset to get back to "your" live id - resetting the dev unlock status.
Ok let's wait for some success here: http://forum.xda-developers.com/showthread.php?t=1078007 - cross your thumbs

Well the way it works is simple...
say i have a dev account, and have 2 devices left I can unlock.
You just give me your device, I connect it trough USB (it does not matter if your live ID is the only live ID on the device!)
with your email, live-ID, contacts and everything.
Once I connect it to the pc, I run the tool and type in MY live ID, now I click unlock and your phone is unlocked trough my live ID.
Now you can run the tools to edit the registry, than connect the device and relock. Edit the registry again (the registry editor should probably be running, otherwise you will get an error message). And your device is unlocked, with your live ID and everything.
my registered devices
The following devices have been registered and may be used to test your unpublished Windows Phone 7 applications. Adding additional devices must be accomplished through Visual Studio, but you may only add the maximum number allowable by your account. You may remove devices from this list at any time by selecting the remove option below.
Registered Devices (2)
SAMSUNG OMNIA4/12/2012 Remove
SAMSUNG OMNIA71/8/2012 Remove
Maximum allowable device registrations: 3
Click to expand...
Click to collapse

Thx Marvin_S for your reply. So you say i don't need to change the live id to unlock the device?
And what about that registry thing, the registry editor should be running and then i can set the dev unlock key to 1 and it WILL STAY instead of relocking? Because i think that you need to leave the device as unlocked in your app hub as you show us on your quote. If you hit "remove" then the phone will be locked the next time you connect it to zune.
Maybe you can give us more details on this. Thanks.

Unipac said:
Thx Marvin_S for your reply. So you say i don't need to change the live id to unlock the device?
And what about that registry thing, the registry editor should be running and then i can set the dev unlock key to 1 and it WILL STAY instead of relocking? Because i think that you need to leave the device as unlocked in your app hub as you show us on your quote. If you hit "remove" then the phone will be locked the next time you connect it to zune.
Maybe you can give us more details on this. Thanks.
Click to expand...
Click to collapse
Yes legally yes, however here comes your regedit into play.
The steps to unlock your device are easy:
- Set up your device with your own live ID (I assume you have this already, this does NOT have to be the same live ID as the devs live ID!)
- Connect your device with your Live ID to your friends computer. Follow the steps then run the Developer Registration Tool from Microsoft, fill in the live ID of your FRIEND who is DEVELOPER registered on his live ID.
- Your device is unlocked... to keep it unlocked run Samsung-Tools or a similar xap on your device which will do those regedits you have quoted above. If you have done these edits your friend can safely remove your device from his developers panel.
Done deal enjoy

Is it realy that easy to unlock any device?
That means someone with a WP7 and his own Live-ID wants to unlock it with my Dev-Account and my Live-ID, we connect it through usb, start developer registration tool and his phone is unlocked...
Edit! You have answered my question before i could ask.
Thank you.

ceesheim said:
not possible.
only the FIRST live ID can unlock a phone and you will be stuck with that account.
that mean that you can't use your own email account for online services and your friends email account is always in your phone.
to change that you would need to hardreset the phone and then the unlock is gone to.
Click to expand...
Click to collapse
This is not true
It does not matter which ID unlocks the phone, it does NOT have to be the same.

Is there any Devloper In Mumbai India with the dev Account i have Dell Venue Pro Nodo Locked i want to unlock it
Thanks

wow that could open a whole market for 3rd party unlocks
like:
registered developer: provide a service to unlock wp7 device for 24h
customer: needs teamviewer or some remote desktop and knowlege about "how to prevent the relock" in most cases advanced config can fix it...
customer provide login information for his remote desktop
connect his wp7 device
developer unlocks the phone with his id and removes it after 24 from the list.
rest you can imagen...
soo.. who want a dev unlock for $10 paypal?
who is the dev to become rich with unlocks?

webwalk® said:
wow that could open a whole market for 3rd party unlocks
like:
registered developer: provide a service to unlock wp7 device for 24h
customer: needs teamviewer or some remote desktop and knowlege about "how to prevent the relock" in most cases advanced config can fix it...
customer provide login information for his remote desktop
connect his wp7 device
developer unlocks the phone with his id and removes it after 24 from the list.
rest you can imagen...
soo.. who want a dev unlock for $10 paypal?
who is the dev to become rich with unlocks?
Click to expand...
Click to collapse
Yeah but what if someone runs a keystroke logger... this will open up the dev's email and password to the customer. Its a form of trust both the dev and the customer will need to have.
I will do it in person, no problem, but you are right it is possible to unlock infinite devices this way. And most of the people who unlock will run these regedits anyway (unlimted sideloaded xaps + prevent relocking)

well yea the plan is not perfect
i dont know enough about remote desktop to tell you if there is any way to encrypt the data.. maybe simple copy paste would be enough, but yeah, your login details would be at high risk, still its simple to change passwords..
microsoft wants $99 and all of your personal data
in some countrys you have hell of paper work and waiting times around 6month
even $50 for a quick paypal unlock is still a good deal for some..
microsoft has to come after (or with mango) with some homebrew unlock thing or people will come up with these kinda services...
heh hell or post a $5 fiverr.com add

hey i want to spend some $$ to unlock my Dell venue pro is there any body can help me i m in India Mumbai Pm me .

Yep i got a pretty ugly vision how this could work out in the end!
1 MS will revoke a “few” developers status whom enjoy WP7 dev. “sanctuary”, even if they weren't unlocking.
2 We never ever going to see through a MS unlocked update for public use, forever we going to stick with market app....
Its a bit boxed up future. don't you think?
I also would like to have full access to my HTC 7 Pro T7576 it came with NoDo oobe.Zune not even find update yet.

seems soon be unlocking problem solved
http://labs.chevronwp7.com/

right on time
but a small fee? that stinks, lets see how this works out...

wow thats good news