Related
Hi all,
I just tried to load the new AIM for PPC2002 on my SER 1.2 XDA and it installed fine, but when trying to run it - it said it was not valid to run on the device..
Has anyone else seen this ??
Yes. In fact, I saw it on the new 4.00.16 T-Mobile ROM. It has the program installed (in 'Program Files' even), but it doesn't work giving the same message, and there's no link to it in 'Programs' either.
Keep in mind this is a US T-Mo software upgrade. The version of AIM that comes with it is for US T-Mo only. It checks your SIM card ID and if you are on any other network other than US T-Mo it will not run. You can do a search online to get the Old AIM client for PPC or you can buy the new one they both work since they are not specific to T-Mo version. I don't know why this is other than this software is avail for download off their website and anyone could get it for free since AOL has now decided to sell it and released a newer full client that also deos AOL Mail.
Hmm another thought is since its in ROM you might be able to overwrite all the .dlls in the \windows\ dir with the .dlls that are in the older version or maybe overwritting the listed files that are diff between 40011 & 40016 with blank text files with same name and changed file ext. This would however require you to remove the T-mo apps from start up incase it looks for any of these files durring start up. There's always a way unless devices stop thinking in x&o/1&0's.
Easy path just find th eold one it's online some where.
OK IMEI-CHECK charge £20 to unlock the phone, and I say fair enough. Why am I posting this? Did you know that their method is probably writing a NEW locking code using some other algorithm? If you run their software, it will inflate and write (about 4K of data if i remember correctly) in the part of the Radio ROM, where you only get access from the bootloader (memory address h'0' to h'10000'). Now here's the thing: I bet if I call T-mobile and ask for the unlocking code, it won't work in my phone, as these guys are actually modifying the Radio ROM without even telling you. Have you guys thought about insurance? For those who don't pay £9.99 or whatever extra cover, what if you pricey and precious pda goes bonkers? I think they should tell you *before* doing anything, about any possible problems.
Come on you guys, someone said he has compiled a few logs/imei numbers. Let's crack this thing, it has been done before for xda I and II, why can't we do it for IIs/IIi?
If that's the case, then I wonder what's in those .uif files they ask you to send back to them? Could it be a backup of the sections of the radio ROM that they're replacing?
Also, if they're writing a fixed set of data to the radio ROM, how come everyone seems to have different unlock codes? Could they be replacing the actual algorithm that calculates the unlock code so that it only accepts certain combinations of codes from them?
-no1
Just had another thought - what if they're replacing code in the radio ROM with code from the Himalaya so that the unlock process then works in the same way as the Himalaya?
Has anyone tried using the xda2unlock tool after running the program from IMEI-Check??? I can't test this just now, so it's just a guess.
-no1
Could they be replacing the actual algorithm that calculates the unlock code so that it only accepts certain combinations of codes from them?
Click to expand...
Click to collapse
Yes I believe that's what they actually do. I tried to run their utility with a debugger but it does not allow execution as long as a debugger is running, nice one IMEI-CHECK. However, I have done a full USB port logging when the utility runs and I found out that they write a new image between addresses 0 and 10000 of the radio rom, and that they also read from 3FC000 the first 4000 bytes, and from FFFEF000 the first 20 bytes.
Yesterday I discovered something odd...after running their application, and by inserting a different SIM card, the attempts counter for the unlocking code had a negative value of several millions. Now I suspect that by writing in adresses 0-10000, i think they replace the default unlocking utility which allows to enter the code.
Another idea I will try will be to run a debugger in the PDA (if I can find one) and see if I can capture the memory address with which it compares the input code.
Come on guys, especially you who did the unlocking utility for XDA II!! Give us some help here!!!!
Zouganelis,
That's excellent that you've been able to sniff the USB traffic. Keep up the investigations!
I wonder why they'd need to read sections of the ROM? If they're replacing the calculation algorithm section of the ROM with their own code, then they should already know how to calculate the unlock code - i.e. they shouldn't need the user to send them back the .uif file.
This makes me wonder if the code they are replacing is just a copy of the code from another device e.g. the Himalaya.
If they are replacing with code from the Himalaya then the unlock process may revert back to how it works on the Himalaya.
Has anyone been able to test this by running the xda2unlock tool for the Himalaya *after* running the IMEI-Check program?
Does anyone have the source code for xda2unlock by the way? I tried searching for it, but it doesn't seem to be available.
-no1
Another thing, does anyone know if it's possible to back up and restore this secret area of the radio ROM using the backup to SD method? I assume that when you dump your radio ROM to SD card it's not including this part of the ROM???
I want to be able to fully restore any bits that the IMEI-Check tool is changing, just in case.
-no1
Come on guys, anyone else trying to crack this thing? We need someone who knows how to disassamble/reverse engineer this log file. It can't be that hard! Also, I think the key to understanding what their little proggy does, is to manage to run a debugger when the unlock program runs. It has some mechanism of detecting a running debugger and it quits if you have a debugger running at the same time. I bet my MDA III that some experienced programmer can overcome this and fool their application? I am running out of ideas guys and I am really against paying these thieves 20 quid for nothing. They MUST have done this using the previous unlocking methods for XDA I and II. Does any1 know who did those unlockign utilities? These guys must help us!!!
Have you tried to run OllyDbg as a debugger tool to see what is happening? Your earlier findings were very interesting...let me study this and get back to you all...
One remark upfront though: I do not think they are modifying your Radio ROM....this would mean that if you upgrade/replace your current Radio ROM, you would be SIM-lock free...and I do not think that is the case...
OK, some initial observations:
1. Lousy software...hard to use for novices...why have the phone enter BL mode automatically (using enterBL.exe)...I think we can do better!
2. Since the phone must be in BL mode, I do think it extracts some info from the radio ROM, but the SIM-Lock could also reside in the Extended ROM, since this is usually customized by the provider?
3. Interesting to see that the same proggie and procedure is used for all XDA-X models
4. Can anyone post a file (output of the proggie) of what they have mailed these folks, as an example?
5. I was always under the impression that the SIM-Lock resides in the SIM itself, so this is a software workaround? What happens if you upgrade your ROMs...you need to go through this process again? Does anyone have experience with this?
Thanks, and let's get this thing cracked!
HappyGoat,
My understanding is that SIM lock is implemented by the phone itself rather than the SIM card.
In the case of our HTC devices, there seems to be a small area of the radio ROM that does not get written to (even when you upgrade your ROM). This area is where the SIM lock is located, and probably other information such as your IMEI number.
This is probably why your IMEI and SIM lock information never get replaced when you upgrade your ROMs. I seem to remember that an older version of the xda2unlock tool was able to change your IMEI number but it got pulled for legal reasons.
When I unlocked my Himalaya, it stayed unlocked even after later upgrading the ROMs, so the state of the SIM lock is being stored somewhere. It can't be on the SIM because what if you change your SIM after you unlock it? The phone would need to be able to read your old SIM to check if the phone is locked!
Zouganelis,
Have you got any idea if it's possible to back up the areas of the radio ROM you mentioned to SD card? Like the current SD card backup method, but getting ALL of it?
-no1
Happygoat and no1,
i am pretty sure they write to the radio ROM some data they inflate from their "unlocking" executable file. How do I know this? Well, when I put a different SIM into my XDA IIs, after I enter the pin code, the simlock application comes up (simlock.exe under \windows\) which checks for the correct unlocking code. Now usually, you have 3 attempts available to do this, before the phone locks and says "contact customer services" or whatever. After I run their application, the counter had a value of -2billion or something, making it impossible to lock it. Interestingly enough, the memory adresses to which they WRITE, are between 0 and 10000. Is it a coincidence the simlock.exe application is 10.5kB? I don't think so!! i think they write their own simlock application to reset the counter, and then they read from 3FC000 the first 4000 bytes, and from FFFEF000 the first 20 bytes. The simlock code MUST be here!! i will post the log from the USB port sniffing tomorrow, as I don't have these files right now. It's pretty obvious to see how the bootloader works. Anyone with past experience especially with CE based devices will be able to figure out how to read these last two chunks of the radio rom.
Here's a link with some interesting files, RED has posted in the past:
http://www.pgwest.com/phone-files/
Username: xda
Passwrod: blueangel
I do agree with no1 regarding the simlock, I think this is exactly the way it works.
no1, I don't know how to do any backup to the SD card, but if you really know what you are doing in the bootloader, try reading from the memory addresses I mentioned earlier.
Keep it up guys, i think we know what their software does, we now need to find out how to read properly the output log.
Regards,
Zouga
Hi zouganelis and no1,
Thanks for the explanations and comments...all makes sense to me now, excellent.
Zouganelis, thanks for the website...that is the stuff I was looking for, cheers!
I do indeed think we are close...will report back later.
So... if they need the .uif file AND the IMEI number, could it just be a case of using the IMEI code to decrypt the contents of the .uif file? In other words the IMEI code is the decryption key??? But what kind of encryption are they using?
I think they used simple XORing in the past for encrypting the radio, OS, and extended ROMs, but this changed slightly for the Blueangel. I wonder if they used a similar method?
-no1
Interesting thought...and a simple one...which explains they can turn around a request so quickly...
You might be correct...the IMEI could bear the encrypted code for simlock or not. Nowadays, encryption standards are:
DES
MD5
SHA
DES is relatively easy to "crack", SHA being the hardest...they are one-way encryptions, which mean they can not be reversed. The only way to get a match is to try...I have numerous proggies for this and will explore this option...
OK, did some more googling, found the following. There appear to be only 3 companies or people who can do this, which makes it even more interesting...
1. www.imei-check.com (UK)
- Download proggie
- Send them back the output and EMEI number
- Receive unlock code
2. Ebay guy (Canada): http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&category=43312&item=5763970199&rd=1&ssPageName=WDVW
- Sends you software
- You will run this software and it will generate a log file (data cable required).
- You'll need to email us this log file and we will send you the unlock code with instructions as soon as possible
Looks like same procedure as EMEI-CHECK
3. www.UnLockItNow.com (Company in Malta): http://www.unlockitnow.com/remote/unlock/by_cable/Pocket_PC/unlock/XDA_IIs_unlock.php
Not sure what process they use, but looks the same.
-----------------------------------------
Then I also came across this interesting story: http://www.modaco.com/index.php?showtopic=200968
This guy writes (edited):
I happend across an official O2 email address that I sent an (abbreviated) SIM unlock request, briefly stating why I needed my XDA IIs to be SIM unlocked, and providing my O2 account number and the handset IMEI number. 30 minutes later and I was emailed back an unlock code.
No ifs, no buts, no questions asked and no payment required.
I placed my Orange SIM card in the IIs, waited for it to boot, entered the code and was greeted with "Unlock Code Accepted." Both dialling out and receiving calls on my Orange account no problemo.
...
Bearing the above in mind, I'm not going to directly post the email address, but will gladly pass it on via PM.
Click to expand...
Click to collapse
The interesting part here is that he only had to give his EMEI number, nothing else...and received an unlock code.
If you take the official route of unlocking your phone through your network provider, all they need is your IMEI number because they can calculate your unlock code from that.
I'm not 100% certain how the process works, but I'm fairly sure the algorithm they use to generate the unlock code is different for each handset manufacturer. I think the network provider either has to send your IMEI to the handset manufacturer for them to calculate the unlock code, or possibly the provider is given a database of unlock codes for all the handsets they purchase. This might explain why it sometimes takes them a few days or weeks to get back to you with the unlock code.
So figuring out how they convert the IMEI number to the unlock code would be another way to attack the problem. Although, I think it would probably be very difficult to figure out what hashing algorithm they're using to generate the code. But if it can be done, then it would certainly make things a hell of a lot easier!
-no1
SH*TE I have been writing a post for about half an hour now explaining the files and as soon as I logged in it was lost. :evil: :evil: :evil: :evil: :evil:
Anyways, here we go again. I am posting the files I promised yesterday. The are three JPEGs which are handwritten notes from the first time I run their application, and a log file from the second time I run the application. Here's the thing: the first time, the software send a read command for the addresses 0-10000 of the radio rom (rrbmc x 0 10000) and store in the x variable. Then it probably compared the checksum with their data, and it didn't match, so they deleted this part of the rom (rerase 0 10000) and they written their own version of it stored in a vector called data (rw data 0 10000). So far so good.
The second time I run the software, it sent again the rrbmc command but this time it didn't erase or written anything, so I guess it does actually what I said before with the checksum.
Another important remark:
The first time I run the software, the software requested some information from the device (rinfo) and the xda replied:
BlueAngel B120 C6B23C704A59520150993080051FF87B
After it finished writing, it sent the same command once more and this time the xda replied:
BlueAngel B120 C6 BE3A709999541E509810802FD775B0
Now the second time I run the application, the rinfo command returned:
BlueAngel B120 C6BC3C70B329B2B1509980809FE49B11
Can these be some form of HEX encryption keys or something?
Happygoat maybe you could use them in your nice proggies?
Anyhow, I think this is all for now. The commands in the logs should be straight forward to understand, it's just the data part which needs real decoding of some sort.
Hope it helps, regards Zouga
Zouga,
Thanks alot for the info...and your patience!
I downloaded a program called USB Monitor, which supposedly logs all data transferred via the USB port...is that the proggie you used as well?
What I want to do is run the IMEI-CHECK program on my device a few times in a row..since it was never SIMLOCKED, I wonder what the output will be...and if they will be different.
I suggest other people run this software as well with a USB port logger, so we can compare logs, and perhaps figure out precisely what we need to do.
Regarding the encryption, I will have a look. I do not think that the data you gave me (C6BC3C70B329B2B1509980809FE49B11) is encrypted...looks like plain ol' HEX to me...will do some more research.
What I think would be the ultimate solution, is to develop an app that calculates the unlock code based upon IMEI number...easy to use, no workarounds, and something I understand: Encryption...
Yes, I am biased...but I am reading up on ass'y code right now to get my arms around this thing...so bare with me...
Hi HappyGoat,
It's good that finally you guys got interested in this! Yes it is the same piece of software I used to sniff the port, it would be interesting to see the output of your unlocked device. Could you please post it as soon as you have it? I hope we can crack this!!
Come on guys, don't just complain for the £20 charge, give us some help here!! We should all run the software and log the data to compare them, as HappyGoat suggested. Then we should all be HappyXdaUsers
Looking forward to some news,
Zouga
Zouga,
Can't download the zip file (bottom one) for some reason...reports that file can not be found...can you try again please?
Cheers,
HG
Hi folks,
Although I am generally not timid about modding certain products (such as my computers and TiVo), I do like to first take my time before diving in until I'm sure I've read most of the relevant threads and have gathered up the complete suite of software tools in one place. The resources on this site and the work of folks such as DCD and nueChem are amazing and outstanding and I want to say thanks for that.
As of yesterday, I felt read to take the plunge installing the bootloader, 3.27 radio ROM and DCD 2.3.2 kitchen build on my XV6800. However, I didn't just go with the stock kitchen. I added a couple of additional OEM packages from Alex.Kaiser.v4.OEM.Packages (the nue LED and audioparam packages and Resco File Explorer 2007 in particular).
The updating went great and I was able to OTA reprogram my phone without needing to call Verizon. However, I noticed that something wasn't right.
First, my phone had no connection data onboard so the phone didn't know to dial #777 for a data link and my attempts to enter this manually didn't give me any success.
Second, my PC wouldn't see the device unless I deselected the "advanced network features" (or similar, I forget the exact wording) checkbox.
Third, I couldn't install CAB files. They'd terminate immediately with an "installation was unsuccessful" message.
Finally, once I was able to establish a connection to the PC, I could add and remove files from the device *only* from the PC. Attempts to delete files from the device itself were met with a file permissions error.
After playing around for a while trying every tweak I could think of, I tried using Resco Explorer and, after a few minutes, got a registration code error/warning message. This made me wonder if this package was the problem: preventing certain types of file access due to it being in a limited-functionality mode from lack of a proper reg code.
So, I rebuilt the ROM without it and now all is well! I'm loving the new dialer and comm manager as well as the active GPS (I've tested it only with Google Maps and GPSToday so far and it gets to within half a block). Not sure how well EV-DO Rev A is working yet. I tethered the phone and ran an online speed check, obtaining 1.2Mbps download but only 60kbps upload. It's possible this is related to my local coverage (Nyack, NY), so I'll try this again from a known-good Rev A area.
Anyway, just wanted to relay my experience in case it proved useful to anyone.
One other thing: I used PIM Backup to backup my data beforehand since my sycing is generally done on my work machine and I was doing the ROM updating from home. Upon restore, it wouldn't restore my email messages because it didn't find the corresponding account. So, it's important to note that this account info isn't backup up and that you first need to create the account before doing the restore step (making sure to name the account the same as before so that it matches up).
David
Hi,
I've found many software that supposed to help in case your phone get lost or stolen.
Some were expensive, some were free, but none fitted perfectly to what I was really expecting. So I've made my own.
The closest in terms of functionnalities (and price) is Remote Tracker, but it requires .NET 3.5 which is not installed on my WM6.5 phone, and honestly, it's a very fat dependency.
The idea is that you install this software (no CAB, simply copy the 2 files on your phone), and run it once to set up the configuration. Then forget it.
In the case the phone is stolen, the software will send you a SMS with the thief's phone number, it's GPS position, the CellID in case the GPS pos is not available.
You'll then be able to act on your phone remotely by sending it some SMS (described in documentation).
The features that makes this software unique are:
It's possible to destroy all your personal data remotely (call log history, contact, emails, SMS, calendar, owner info, storage card) -> help social engineering to get back your phone.
It's possible to make the phone send you back the call history and the sim contacts.
Slut mode (see the documentation for details).
WOULDYOUSHUTUP mode (where the phone is very very nasty).
All other tracking software features...
This software is open C++ source (GPLv3), small (75ko with no dependencies), and free.
You'll find it at http://dsmp.sf.net (documentation on that page)
Or the direct link is attached.
Beta tester welcome (I've tested all functions already, but, you know what software development is....)
Some remarks for those who don't read threads:
whereRU: requires you to have at least a .wav file in your windows ring folder. I thought all phone had at least one .wav based ring. In 64kb, I haven't included a MP3/AAC/MP4 player.
owner: This is what I said in my first posts. Microsoft didn't feel it was interesting to document how to retrieve owner info. So, almost all manufacturer have made there own proprietary stuff. I've a HTC phone, so I've checked the code work for HTC. If you have more information about where your phone store its owner information in registry, I can add your phone support.
contact: On the main config dialog, in the combo box where you can enter the phone number to contact, you'll have a phone number list. It's the same list as returned in the "contact" command. So if you don't have such list in the config dialog, then this means that either you don't have any contact on your SIM card, or it's not working (in that case PM me).
Please read the website http://dsmp.sf.net
To install the software:
1. Extract the zip file (either on your phone, or on the PC, and then copy the 2 files from archive to your phone)
2. Run the extracted exe on your phone. If you have signed warning say yes.
3. Set up your configuration (DON'T check "Don't show this screen anymore")
4. If you have a GPS in your device, go outside to make sure the GPS is working with the configuration you've made
5. Enter a (not yours) phone number in the SMS par edit/combobox
6. Enter a password in the edit box on the bottom
7. Click done => Say yes.
8. Start the software again, enter the previous password in the field on the botton to unlock the dialog, then click on "Configuration done, install now"
9. If you have signature warning for the DLL say yes.
10. It should display "Installation done". You can then send yourself a SMS with the right format to check if it's working.
11. If it's working, delete the SMS you've just sent from your outbox, and trash, and then start the software again and check "Don't show this screen anymore". You'll have to click "Configuration done" again, but this times, you shouldn't have any warning.
12. If it's not working, well post on the forum.
Changelog:
- Added "allow" command so it's possible to use multiple allowed SIM card. Setup the software as described above, and then change your card. You'll get a SMS with the new number (if not, your configuration isn't good). Then reply with the command "dsmp # allow # password" with no space between #. This SIM card is then allowed. You can have up to 4 allowed SIM card.
- Fixed an installation bug on non-french phone. Sorry, I've been lazy, and it should be fixed.
- Added support for "Dsmp" in addition of "dsmp" as trigger code
- More owner info retrieved for HTC phones
Please go to sf.net page ( http://dsmp.sf.net ) if you want to get the debug version or source code.
sounds impressive ! i might give it a try!
good work !
CDMA diamond running a 6.1 rom. got to step 8 and each time I enter in my password and close my keyboard the screen where the keyboard was (touchpal is my SIP) shows the screen behind what it should show. hope that makes sense. how do I uninstall this software?
also, I dont see anywhere where it says what WOULDYOUSHUTUP mode is.
WOULDYOUSHUTUP is what happen when you send a sms with "whereRU". The phone rings at max volume for 60s with no possible way to stop it, even if it was in silent mode.
Useful when you've lost your phone nearby, (it won't stop until you've found it, or 60s later), or, as intended, to become a nuisance to any thief in the middle of the night.
To uninstall the software you must click on "Zap" button, but you need your password for that. BTW if you haven't done step 8, you don't need to uninstall, as the installation proceed only when you click "Configuration done" button.
If the software doesn't accept the password you've set at step 6, then it's likely that it was entered wrong at first? I'll PM you about this, if you don't mind.
installed it, and tested a whereRU with another phone, doesn't work. :\
I've answered with specific details by PM. I trying to understand why installation didn't work for you. I'll update the post with the informations you'll give me.
sounds really nice.
I just see some problems. These problems apply to any anti-theft program :
If you have a pin-lock for the device (not sim card lock, the built-in windows lock), the thief will not be able to change anything (owner, ...). He can only change the sim and try to boot, what will of course fail. As this fails (without unlocking phone-lock, no dialing), he will not be able to establish a connection to his mobile network and you will not get his number (?!)
As hard-reset is always possible (every thief can google ) w/o the program being cooked into rom, this software is senseless if you can't cook roms. I can't
If I understood it correctly, you would need to edit the 2 files to your needs (with numbers aso) at first instance and afterwards cook them into rom. This has to be done by each end-user each time he flashes a new rom and cant be done by rom-chef because he doesnt know your data.
Isn't it possible to make that wireless? E.g. you specify an email there and the programm will at first boot after hardreset (after cooking into rom) establish a connection to a server (or mail to specified mail) to download the details (cell number, pw, ...) you entered in the server? ^^
You only can enter one own cell number. Bad if you sometimes switch the sim's.
Would be better to implement that from remotetracker:
SIM Cards: you can set up to four known SIM cards. If you, or anyone, change the SIM card to an unknown card, your emergency number and e-mails will receive a message alerting you about the change and with the new number
Click to expand...
Click to collapse
* If you use this kind of software, you'll want to make your thief believe he succeed owning your phone. If you PIN-lock your device, then the thief will have to hard reset the phone to use it, defeating the whole process.
* In my previous phone (Universal), there was a Extended ROM made by the operator that survived hard reset. I've used that ROM by that time.
Now, you're perfectly right, with a single ROM, the hard reset kills the software. Your idea of using a external server is genius. I guess I'll add this, using your device ID (which doesn't change whatever the ROM) (or IMEI), to retrieve the config for your phone. The config will be saved on a server, and the config can be sent back by SMS (so even if the thief doesn't have network contract, it'll work).
* You switch SIM ? Is 2 SIM okay ?
I wanted the software to be extremely simple to setup, so it detected the IMSI by itself.
Now, if you need to store 2 IMSI, it'll need another edit box to let you enter the IMSI numbers.
I can add a new command "allow" that, when you've inserted your second SIM, will allow the new IMSI upon receiving.
Let me think about this.
Yep, but I won't -of course- disable excellent built-in security mechanisms to make it *perhaps* easier to get the phone back just in case someone steals my phone.
The phone-lock is ideal to keep away random access to private and corporate data from other persons (friends, aso).
Despite the lack of some functions I installed the program yesterday and it doesn't work as thought:
The program loads after each reset again with the config screen
The program is active in task manager (dsmp.exe)
The sent commands aren't executed. If I send the commands (e.g. rst or whereRU) to the phone, the display turns on but nothing happens.
(perhaps the first 2 problems are caused because I did not hide the program yet with "Do not show this anymore" Not sure about that )
You could just say at setup: Now turn off the phone and enter your other sim and start the setup again to detect the second sim
hi popol256,
is there a chance for a very thin application, that after installed on a phone (e.g LEO) makes JUST the following:
- receiving a predefined SMS lock's the phone and encrypts the msd card.
To unlock the phone and decrypt the msd card, just a so called "master password" or whatever needs to be input.
That's all
thank you,
/s1
Locking the phone is possible (but again, if you lock the phone, then the thief will hard reset it).
Encrypting the microSD card is not, I think.
So far, I think you need to either encrypt it at first use (all WM6 phone have this as a base feature). When you have data on it and want to encrypt, it's almost impossible as you'll need the same free space on your device as your card size to store the encrypted version.
(Or if only encrypting content, you'll need to reserve half your card size for the "possibly" encrypted archive).
I guess the best method for you if to use the storage card encryption feature of WM + pin lock.
bliblablub said:
Yep, but I won't -of course- disable excellent built-in security mechanisms to make it *perhaps* easier to get the phone back just in case someone steals my phone.
The phone-lock is ideal to keep away random access to private and corporate data from other persons (friends, aso).
Click to expand...
Click to collapse
You are right. The only way to have both would be to cook your own ROM with the software inside.
bliblablub said:
Despite the lack of some functions I installed the program yesterday and it doesn't work as thought:
The program loads after each reset again with the config screen
The program is active in task manager (dsmp.exe)
The sent commands aren't executed. If I send the commands (e.g. rst or whereRU) to the phone, the display turns on but nothing happens.
(perhaps the first 2 problems are caused because I did not hide the program yet with "Do not show this anymore" Not sure about that )
Click to expand...
Click to collapse
Yes the 2 first issues are because the config says to show the dialog.
The third issue means that the software isn't installed well.
I've only tested it on my phone, and I might have done something wrong.
There is a debugversion here
Extract this version to your card, then run the exe in it, and click "Zap". Then wait for few minutes, and reset your phone (this is to make internal mail application to release its lock on the interceptor DLL).
Run the software again, and set the config, click "done" or "ok", and send yourself a SMS (don't need to install this version, it runs from the card).
You should get 2 message box, the first one contains the path to the software (end in .exe), and the message you've sent, and the second only contains the command you've sent. If this work, well, I'll have to double check the release version.
bliblablub said:
You could just say at setup: Now turn off the phone and enter your other sim and start the setup again to detect the second sim
Click to expand...
Click to collapse
Yes, it's the basic idea (in fact, as soon as you insert your second SIM, you'll receive a SMS, but you'll then send an "allow" command to add this IMSI in the allowed IMSI list). I'm adding this.
Hehe, got the following error running the debugversion:
CmdLine (OK)
(empty)
Click to expand...
Click to collapse
Can't load DLL (OK)
\Carte de stockage\DSMPI.dll
Click to expand...
Click to collapse
Error (OK)
Can't register the message interceptor DLL
Please make sure the DSMPI.dll is in windows folder
Click to expand...
Click to collapse
Ok, my fault then, I've used French name for the path. Let me few hours to compile a new version with the regular name, I'll post back here.
Ok, I've added the "allow" command for multiple sim card. The idea is simple, configure your software as said in the first page, then change your sim.
You'll received a SMS to the number you've set up. Then send a "allow" command with your password, and the new SIM is allowed you'll never receive a SMS again.
bliblablub,
Please run the version you have on your storage card, and click "Zap" button to uninstall it.
Then delete the 4xxxxxxxxx_dfed_p (xxxxx is a hexadecimal number) from your storage card (file format changed).
Then download the updated DSMP.zip version from the main (or the official) page again.
There was a bug with the file path that should be fixed now with the release version.
Thank you for your patience.
popol256 said:
bliblablub,
Please run the version you have on your storage card, and click "Zap" button to uninstall it.
Then delete the 4xxxxxxxxx_dfed_p (xxxxx is a hexadecimal number) from your storage card (file format changed).
Then download the updated DSMP.zip version from the main (or the official) page again.
There was a bug with the file path that should be fixed now with the release version.
Thank you for your patience.
Click to expand...
Click to collapse
I can't uninstall it because it was not installed I guess (debug - storage). See errors on post before
Somehow I managed to uninstall the internal version. Needed several attempts.
Now installed again on phone and again nothing happens with whereRU and any other command except lcd turning on
Does it work fine?
Any opinion?
Nice, nice, nice. Sounds like the app I was always looking for. I will download and try. Thanks
It seems to work fine on my X1.
But gps is not recognized on port 4 baud 4800...
[Q] TomTom Navigator "You have an invalid version of the TomTom application"
Does anyone know WHICH build of TomTom is the "correct" one for the HTC HD2 (or HTC Leo as TomTom sees it)?
I have;
ApplicationVersion=7916
ApplicationBuildNumber=9189
and have tried many others, and whilst they work perfectly on the HD2, TomTom Home simply won't accept any of them as valid.
Hope someone can help!
Grey Area said:
Does anyone know WHICH build of TomTom is the "correct" one for the HTC HD2 (or HTC Leo as TomTom sees it)?
I have;
ApplicationVersion=7916
ApplicationBuildNumber=9189
and have tried many others, and whilst they work perfectly on the HD2, TomTom Home simply won't accept any of them as valid.
Hope someone can help!
Click to expand...
Click to collapse
This version does work good on my HD2...
For TT Home extract and replace file in attachement on your phone
OK...little confused...on my phone or in TT Home on PC? I already tried a new mobile.ddf file in my Home/Resources folder, but it didn't solve the problem.
Copy ddf file in PC folder "Program Files\TomTom HOME 2\Resources\Devices".
Enable Map share in TT in phone.
For me it does work without problems.
Unfortunately not for me. Mind you I think I have device code problems too - when i first installed TomTom Home it worked okay, but now even though I am using the same device I am getting a different serial number - but only very slightly different (it's exactly the same 32-character code, but the one that my account has registered has a "T" in front of it and lower case letters instead of uppercase).
TomTom of course has their stupid "one change in 6 months" rule, so I guess I just have to wait...
TomTom supposedly unlocked my account, but I still can't update it with the new device serial number.
Anyone got any other ideas on how to get aroudn this problem?
Thanks!
Do you have Tomtom installed to your device and not the SD card. I had the same problem untill I reinstalled the Tomtom app to the device, but left the zip folder, voices folder,art folder, and map folder on the SD card. Now Tomtom home works perfectly with my HD2.
Using Tomtom app 7.918 (9193) with latest 860.312 Western Europe map
*EDIT* Yes it WAS worth a try - R12SRW you are a genius...haven't tried to see if EVERYTHING works yet, but at least the stupid error message hasn't appeared.
*EDIT #2" Seems faultless now - MapShare and speed camera updates automatically found and downloaded...thanks again!
That's worth a try I guess...only problem is the memory on my HD2 is so damned tiny...
Will try it and let you know what happens.
Excellent Advice R12SRW!
I uninstalled TomTom Navigator from my phone as I had it installed to the SD memory card and and reinstalled it with the "Install to Device" option.
Now when I connect to TomTom home I have all the map share updates and other options and that "You have an invalid version of the TomTom application" error message is gone.
Thanks alot
R12SRW's Solution worked for me, I'm smiling again!!!!! Thanks.
Mapshare updates installed and load of previously greyed out options are now available.
Had to reset all options in Tomtom once reinstalled to internal memory but all voices, favourites etc remained available so well happy.
Using Tomtom home to 2.8 and navcore 7.918.9193 with latest v865 maps
Reinstall on sd carte
Hello.
I have the same probleme. Does that work if I reinstall on sd carte ?
Tomtom Navigator tt7.918.9193
Western&Central Europe 2GB 850.2801
Thank you