Related
Has anyone seen the CDMA version yet? They were in Pocket PC Magazine (Feb issue).
I am curious as to which BT version they are running (1.0 or 1.1)
Funny reading the article, they stated Sprint was the first to bring this phone to market in the USA...funny, I have had my SX66 since December 04...unless they are talking about the CDMA version! (grin!) The "manufacturer" for the phone is Audiovox. It is also on the Audiovox website, with a Verizon version listed both With and WITHOUT the camera...along with a listing of accessories we can purchase!
Tom
cdma ppc-6600
I am a network admin for a large insurance agency, we have 30 new ppc-6601's and 2 ppc-6600's. Yes these are Sprint Phones and I have already upgraded the ROM versions and the Radio versions. Some of the phones have been having nothing but problems locking up and dropping calls and the rest are fine. As far as the BT version it is 1.0.0.3500 except for the BtCeStack which is 3601 this is with the new Version ROMs.
My phone personaly is
ROM: 1.36.00
ExtROM: 1.36.113
Radio: HA00_140
BtCeStack: 3601
Wish it was GSM and not CDMA, not big on Sprint but well thats what we have
CompUSA, in Sunday's newspaper ad, lists the 6600 for $629.99, with $250 in discounts with Sprint activation.
any chance you can post the splash screens and any sprint specific windows themes
Re: cdma ppc-6600
wififreq said:
ROM: 1.36.00
Click to expand...
Click to collapse
There is already 2.03 version. I don;t remember the version of radio
Re: cdma ppc-6600
mamaich said:
wififreq said:
ROM: 1.36.00
Click to expand...
Click to collapse
There is already 2.03 version. I don;t remember the version of radio
Click to expand...
Click to collapse
Where is the 2.03? On the FTP server?
Thanks to mamaich:
ftp://www.clubimate.com/Support/HA_Telstra_20300_111_01140.exe
it is for Harrier devices (CDMA):
ROM version: 2.03.00 WWE
ROM date: 12/15/04
Radio version: HA01_140
Protocol version AA3.3.301
ExtROM version: 2.03.111 WWE
I'm still trying to figure out how to get it installed on my Sprint 6600. I'm getting the Country error 120 and haven't yet figured out how to get around it. The suggestion in the Blue Angel FAQ of editing the RUU.conf doesn't work because "[CHECKCEID_TYPE]=1" is already in the file.
I'm excited to try this out since it's got Windows Media Player 10 built-in.
Dan
This sounds very exciting. I myself have a Sprint PPC-6600 and would love to get this working as well. I noticed that this is for the Harrier device and not the BA. Will this still retain the hardware keyboard? If you get it up and running smoothly please post the process you went through. Good luck!
Difference Between Harrier and Blue Angel.
There is no difference has I have both the Sprint PPC6600 and XDAs, the only difference is that the Blue Angel has Wifi and is GSM, and the Harrier is CDMA with GPS and no Wifi. The Specs and design are exactly the same.
The Harrier is not easy to unlock has the ESN and MSL/SPC Code is stored on the Qualcomm MSM5500 Chip. The only way to access this chip is from accessing the PDA COM2 Port with a new multi access serial driver, as the one supplied only allows single entry from wince only.
If we have got some good Win CE programmers out there who can make software to read this chip so we can access the MSL/SPC unlock code which is 6 digits.
There are 2 stored in the chip, one is the one time access code and the other is the main code.
So A lot of people across the globe using these HTC devices on the CDMA network would be grateful if this software was made available or even sold at a reasonable unlock price.
If anyone has a solution to unlock these CDMA versions please email me at [email protected]
Thanks
Re: Difference Between Harrier and Blue Angel.
syrixcom said:
There is no difference has I have both the Sprint PPC6600 and XDAs, the only difference is that the Blue Angel has Wifi and is GSM, and the Harrier is CDMA with GPS and no Wifi. The Specs and design are exactly the same.
The Harrier is not easy to unlock has the ESN and MSL/SPC Code is stored on the Qualcomm MSM5500 Chip. The only way to access this chip is from accessing the PDA COM2 Port with a new multi access serial driver, as the one supplied only allows single entry from wince only.
If we have got some good Win CE programmers out there who can make software to read this chip so we can access the MSL/SPC unlock code which is 6 digits.
There are 2 stored in the chip, one is the one time access code and the other is the main code.
So A lot of people across the globe using these HTC devices on the CDMA network would be grateful if this software was made available or even sold at a reasonable unlock price.
If anyone has a solution to unlock these CDMA versions please email me at [email protected]
Thanks
Click to expand...
Click to collapse
I don't know about Verizon, but Sprint always gives you the main MSL (not the one-time) when you activate the phone. Do the other carriers somehow program your phone OTA? How else do you get your MDN and MSID in the phone?
I know BitPim can get the MSL for a lot of other Sprint phones... maybe the developers can make it work with the Harrier.
Sorry I can't be of more help here.
Dan
The 2.03 upgrade works great on XV6600s and PPC6600/6601s.
http://www.myehud.com/ppc6600/upgrade
(This was covered in the Blue Angel Upgrade forum in the Harrier is a Red-Headed stepchild thread...)
Ehud
Sprint 6600 Users Upgrade to Win Media 10
First of all download the Telstra Rom Image, Unzip with WinRAR.
Copy the attachement below to the directory. Now sprint users you need to copy the radio image file from the sprint download and copy into the telstra directory.
Press power, record and reset button to put yourselve in bootloader mode.
Run the attachement you downloaded
And you should have a working telstra image.
If you don't change the radio image you have no signal, because sprint have disable evdo in these phones.
yes that is the correct procedure. Do keep in mind there are some other changes in that ROM, but more or less it works OK.
Dan
Can I also put the latest extended rom for my phone in this directory to have it update that at the same time too?
elkay said:
Can I also put the latest extended rom for my phone in this directory to have it update that at the same time too?
Click to expand...
Click to collapse
Yes you can... and I would suggest doing so (or at least deleting the Telstra ms_.nbf( unless you want i-mate/Telstra branding!
Dan
I can't wait until I can start cooking my own rom. I'm having a ball with all of this.
I have an XDA IIs from O2 and a Qtek 9090 from Vodafone (fairly litlle tinkering from Vodafone).
I want to unlock the XDA IIs (as does everybody else) but isn't the SimLock part of the Radio Rom, in which case cant I jusr replace this with the Voidafone Rom and hey presto!!
I am sure that this is not as simple as I have suggested, or everybody wouyld be doing it, but can someone explain to me where the SimLock subsystem is and therefore where I should start to poke, to unlock it.
I quite liked the idea of sending millions of AT commands to the wireless modem, but that sounded too easy as well.
I know what the Extended Rom does, and the Rom Rom (presumably OS), and in general I know what the radio Rom does, but if this is all there is then I cant see where the SimLock stuff would be held???
If you could reply I'd be grateful, and if anybody reads this and cracks an unlock, drop me a line as well.
Thanks in advance
During a lot of months I have been wondering this. In my opinion, I think that simlock is in the extended rom because it contains special programs from your provider, but I am not sure. The definite clue would be to change all the operating system (radio rom, OS rom, and extended rom) for other (for example, qtek 9090). If somebody knows how to do this and he tries it, please let us know. Thanks.
The code in the CE ROM (Or possibly the radio rom?) reads information from the phone hardware to detect if it is locked or unlocked and merely displays a message to the user indicating its current status when you try to use an alt network sim. The lock status, network locked to and unlock code is stored in a separate flash area of the phone hardware within the XDA IIs - not in one of the standard 3 roms.
This means that no matter what "standard" rom you put on the XDA it will not suddenly become "unlocked" (As I have had numerous different roms on mine since I purchased it - radio, ce and extended rom).
Unfortunately the area of the phone containing this information cannot easily be accessed and requres a code based on the IMEI number of the phone to access. Without the algorithm used to calc this code (Different for each phone type ie alg. for XDA II is different to one for XDA IIs) we cannot unlock the phone!
That said, I believe that the phone itself may not actually prevent the calls merely the firmware in the radio rom after detecting that the phone is "locked". Therefore, I believe it MAY be possible to hack the rom to allow it to be used on any network. PLEASE NOTE THAT I DO NOT KNOW THIS LAST BIT OF INFO FOR SURE, IT IS SPECULATION ONLY AS A POSSIBLE WAY AROUND THE SIM LOCK....... NOW WHERE IS MY HEX EDITOR!
A summary so far
Ok,
So the simlock code is contained in a fourth ROM somewhere in teh device that we dont know how to get to. The radio ROM then somehow reads to see if it is locked, and if it is prompts for the unlock, and if not then allows you to make a call etc.
This fourth ROM is likely to be pretty fixed, like the deviceID and is presumably unaccessable to anything without opening the device up, removing the chip and hitting it with a lightning bolt.
So where does that leave us. The screen that comes up about SIMlock, enter the number, which interestingly enough says that I have tried a large negative integer times, and then locks up permanently (or so it seams). This bit must be in one of the accessible ROMS, as it is too Windowsy for anything hardware wise.
This screen must call some other function that tries the unlock code into the unaccessable chip. It would probably be easier to attempt to remove the retry timeout and then retry millions of times, either with a simple sendkeys type function or with something cleverer. Or alternatively find the function that SIMLock calls to the hardware.
I am being creative here, hoping that someone can step in and be a little more factual. Anyone....
On the XDA II, if you unlock it, can you lock it again?
Think of this fourth "rom" more as as a type of BIOS with basic hardware call functionality with windows and radio rom sitting on top providing code to access the "BIOS" for radio functions (Bluetooth, GPRS, WiFi, GSM etc) and hardware functionality (LED's, buttons etc). It has a form of NVRAM with IMEI number stored as well as SIM locks etc....
Hi all.. This is my first post so obviously this is a newbie question! My XDA 2s is not able to recognize the name of my mobile operator here in India, and it shows up as "40468". Is there any tweak by which I can manually feed in the name of the operator so it shows up on the Phone screen?
Just to explain the issue clearly - the number on the top right is where the name of the mobile service provider should show up. Why does it show up as a number (40468) and not as a name, as it did on my Sonyericsson P910i, or indeed other phones? Grateful for any help in this matter.
It's because basically each mobile phone operator is allocated a number (in your case 40468) and inside each phone is a tiny database of operator names/numbers.
I used to think that the operator "sent" the name, but a few years ago now a UK operator changed it's name from "Cellnet" to "BT Cellnet" and then to "O2", however phones wouldn't change. But if you had a newer version of firmware on your phone it would change (so that supports my theory that the database is in the firmware).
I think this also make sense because the operator isn't going to know how many characters are available for showing the name/abbreviating as necessary and so it makes sense for the mobile phone providers to keep their database in sync with the "main" one for who is allocated what as it'll make sure the information is displayed correctly as they can abbreviate as needed for each device.
At least that's how I understand it. So in your case it sounds like your phone doesn't know your provider. Perhaps a newer upgrade might help (1.33 or 1.40?), but I'd just ask your provider. If they sold you the phone it's pretty weird it doesn't support their own network. It might just be a faulty handset :-(
Perhaps post the name of your operator and we can see if anyone else is using them and it works for them
Neil -- many thanks for your reply. When I bought this phone (unlocked) from Kuala Lumpur, it wasn't as yet available in India. Now it is, though. Maybe thats why it doesn't show up all of India's mobile service providers. Anyway, my mobile provider is MTNL in Delhi.
Upgrading ROM to 1.40 may solve the problem, provided its and "Asia" ROM. Is that available yet? Is it possilbe to "cook" the rom to add service providers?
Many thanks for your help Neil.
Well you're using PH20B which is same as my phone is here in the UK and I'm running the 1.40 ROM so technically you shouldn't any problems. I'd wait for someone else to just verify either that A) What I've said about being stored in the phone is correct or B) Some one using MNTL in Delhi to confirm they have/haven't got this problem.
Because if it's a case of it's fine for them and ROM's are same etc it might be a faulty unit (can't really see how!) and a ROM upgrade might not help and since technically these ROM upgrades aren't always official (1.40 probably isn't) you'd probably have to put it back/find previous ROM before you could take it back.
Upgrading to 1.40 isn't really a pain, see the WIKI (top left) it's daunting at first, but it's actually very easy to do, but do it when you have enough time to reinstall everything because doing any sort of ROM upgrade does a hard reset as well (wipes everything in main memory - \Storage and \Storage Card are safe).
I can't guarentee that this would fix your problem, i.e. your provider is in that ROM, but not sure what else to suggest + 1.40 does come with Media Player 10 which is a bit of an added bonus! You can backup your existing ROM, although it's probably already on the FTP, might be handy to have it in advance if you want to go back.
Hope that was some help!
P.S. If you decide to go down the upgrade route, probably worth upgrading your radio at the same time. I'm all the way to 1.12 and it's fine for me, but some people seem to have stayed with 1.10 because they've had some issues - search forum on this)
Neil -- two quick comments.
One, from using cell phones for the last many years, I feel that the code to decipher the cell provider's number is in the phone. This has happened to me before, when I bought phones which were not available in India, and it's happened again! It seems to me it's a ROM issue, as its logical for cell providers to be consistent (i.e. broadcast their identification numbers) and let the phones decipher them.
Two, is there any major danger that I'll lose the phone itself with a ROM upgrade? I know this has been answered in some other threads of this forum, but it'll be a first for me on this newly acquired beauty!
Cheers and many thanks....
example:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RIL\OperatorNames]
"45404"="3-DUALBAND-"
Hehe, big mamaich spoke... :lol:
Yup, those are PPC's: many things can be done by software... :wink:
This is odd...
Since I upgraded my MDA2 to 2.06.00WWE Radio: 1.14.00 I've seen this problem where the carrier name was changed to a number (in my case 334020).
On my previous ROM version I had no problem at all. And this device does not even exsist in Mexico and it displayed the carrier name (Telcel) without a problem.
I think the carrier name is taken from the network itself and fed to the registry but this particular ROM has problems taking this particular carrier numbers.
If I do a network search I can see the other carrier in my area (Movistar as a number also) and two other United States Carriers (Cingular and AT&T) but this time with their names (I live close to the United States).
To "fix" this I created a GIF file named carrierlogo.gif and place it on the Pocket PC Windows directory and now it shows a nice Telcel logo instead!...
@ Rayan
that looks good! Could you please explain how you did it? The first step obviously was to place it on the Pocket PC Windows directory, but what were the other fixes? Did you tweak the registry? Newbie question... I've been a XDA 2s user only for a few weeks Rayan!!
mamaich said:
example:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RIL\OperatorNames]
"45404"="3-DUALBAND-"
Click to expand...
Click to collapse
Mamaich speaks loud and clear! Yup, adding that additional string did the trick! I created a string for my carrier ("40468"="MTNL"), did a soft reset and Voila! It worked! Thank you Mamaich, thank you forum!!
Hi Dilip,
I tried the trick on my PDA2k, but not worked..can u pls elaborate how u hv added the string....or made a new key value in the registry?
hdubli said:
Hi Dilip,
I tried the trick on my PDA2k, but not worked..can u pls elaborate how u hv added the string....or made a new key value in the registry?
Click to expand...
Click to collapse
it works and thanks to mamaich (he is the greatest) i tried it on my imate jam and worked like a charm.... all u have to do is navigate to
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RIL\OperatorNames]
using any registry editor like resco..... once u reach OperatorNames create a STRING VALUE
in the Name box write the number that shows in ur dialing pad and in the String box write the name of the operator or any name u want ..... look at the pic ... and u can write it in any lang u want
As shown by PapaDocta above, I added a string to my registery and this is how my phone looks now:
Hi!!!
Thaks, now it worked...I was trying to make a new key value and what not.....but never knew that it was so simple.
Thanks a ton..This helps very much during roaming...
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?
guys,
when I moved from WM5 to WM6 (both official ROMs), my device ID appeared to change (assumption by virtue of the fact it changed in TomTom 6).
Can anyone else confirm they have seen this? I'm still waiting for HTC UK support to contact me. ABout a week now.
I thought it might be helpful to see who has seen this (regardless of ROM details).
Hi,
Yes, all time you Flash your PPC with new Rom, Your Device ID change, and Tomtom need to be change too (Trafic, SN, etc...)
If you have Tomtom Trafic option, go to tomtom site to change your device id, it's work fine.
As far as I know, it is only the DOPOD, and DOPOD based ROMs that have this problem, and it is a bug in the firmware. The very latest DOPOD release has apparently fixed it- so Mun's Indigo Full which uses the latest ROM is OK, but Lite shows the problem.
Device ID's are a complex matter. Some are based on the IMEI, some derived from the ROM version and some by other means. TomTom and Mobipocket both use 'other means' to derive the Device Code, and it is only with the 'faulty' ROMs that the Device Code changes.
I've taken my Trinity through about 7 ROM updates, and the TomTom Device Code remained the same except in the DOPOD WM6 ROMs; reverting to another ROM resulted in the Device Code going back to what it should be.
This is a real problem for TomTom users because they are currently refusing to relink the new Device Code to the Traffic and Weather account, even if you succeed in obtaining a new activation code. So you have a situation where the software is working fine, but you can't access your TomTom Home subscriptions. Customer Support are now asking for 'proof of purchase' of the WM6 ROM upgrade, which of course can't be provided as there is no 'proof of purchase' for most ROMs.
We have had quite a long topic on this on 4Winmobile, and the latest situation is that it could be a case for Trading Standards to investigate, as TomTom are effectively blocking users from accessing services they have paid for.
hi Neil,
that's most interesting feedback, thanks.
I too have installed at least 6 ROMs on my Trinity. From the OEM Orange UK WM5 (the phone came with) through to mUns TE and others the device code remained static.
Then when I went to the officical Dopod WM6 ROM it changed. I believe I also used the latest official of their ROMS the other week, which was rumoured to fix this issue, but it has not. I think people are confusing the other issue of changing with each hard reset- which I do not have the problem of.
I'm very frustrated with TomTom- it's a month now with no Traffic- and I use it for my work driving the length of the country.
I've suggested that it shouldn't be my problem- after all I have paid the subscription, and it's an official ROM. OK it costs them time to make a change- but it costs them more to keep sending emails to-and-fro asking me for proof etc etc. I've wasted hours on this chasing, HTC (Dopod), Microsoft and TomTom, plus investigating on the web. It's clearly an issue, but no-one will hold their hands up.
If someone could post a link to the latest Dopod ROM which definitively does not change the ID I'd be eternally grateful. And by definitive, I'd prefer first hand experience ;-)
folks,
tonight I bit the bullet and installed mUn's Indigo Full. Very quick to install, nice looking ROM but the Device ID has still changed :-(
So every Dopod official ROM and now the full Indigo changes the device ID from the original WM5 ROM and every other WM6 ROM.
I've tried 3 ROM in 7 days now. This is getting silly!
I think I will not be renewing my TomTom Traffic. Oh and I forgot to say, HTC Europe sent me a fob- off email tonight.
"Contact your phone supplier......" Thanks. They seem to be deliberately avoiding this- I gave them the chance to just say "yes" we know there is an issue. That would be enough for TomTom.....
TomTom and license key
I have heard that TomTom only allows the use of the license key twice. Has anyone found this to be true? Because, if so, a lot of people who have installed WM6 on their Trinity and have been asked to activate Navigator again (myself included) will have to think twice before switching ROMs again.
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
sickboy555 said:
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
Click to expand...
Click to collapse
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
oh no Pietrucci, that's bad news. And very odd if they changed the ID, but going back to another ROM with old ID, Traffic works.
So if TomTom update my device ID and Traffic still doesn't work I'm scuppered.
Apparently they never let you go back to an old ID in your account, which means going back to an old ROM may not help either. Maybe there is something wrong with their account system for Traffic, if your old one still works???
pietrucci said:
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
Click to expand...
Click to collapse
I have exactly the same problem. Online my plus services shows that the TomTom Device ID is correct, BUT traffic still doesn't work.
Going back to the older version of WM6 with the older device code and it works. So TT Plus servers must still have the old device code associated with my PLUS account even though PLUS online is showing the new code.
I've told TT that it's not working but no fix so far.
MAJOR UPDATE: New build of WM6 fixes the device ID change issue. The device ID is the same as in WM5 - the first cooked ROM to include the fixed build is Schap's 3.60a.
Best get onto TT and have that code reverted back sharpish!
hi eaglerest can you post a link to the specific new build of WM6 you are referring to please (the OEM ROm, not the cooked one).
The 8th of August DOPOD rom DOES NOT fix the device ID bug.
i.e. this one RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship
hi,
sorry it's a hermes build.....
http://forum.xda-developers.com/showthread.php?t=322905
ah, so it's not just confined to the Trinity then.
thanks for the info eaglerest.
right, I've given up with this ridiculous Device ID business!
I told TomTom to leave the ID alone (after 6 weeks with no Traffic) and have gone back to mUn's TE, which preserves the old Device ID.
Not what I really wanted but I think I'll be an old man before it gets resolved.
HTC In Asia and Europe fobbed me off and wouldn't even acknowledge this as an "event" let alone a bug.
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
moondevil said:
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
Click to expand...
Click to collapse
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
TomTom will only change the registered device if I can provide proof from HTC or someone else that this is a bug. Guess what- they've been no help at all. Neither have Microsoft or Orange.
sickboy555 said:
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
Click to expand...
Click to collapse
OK, just so I'm clear on this because I'm (nervously) about to go down the path of updating for the first time. I'm coming from WM5, having never flashed before, will upgrading with Bepe's latest of .74 change my Device ID or not?
probably, but I have no idea for sure. Not used that ROM.
If you use TomTom Traffic and it does change, you will not be able to use it anymore. If you have never changed your device ID with TomTom, you can do it yourself- but only once per 6 months via your account on their website.
You will have to re-register all your maps too.
If you saw moondevils post, his ID changed with one of bepe's builds. I imagine that bepe uses the same core OS for all his builds so your ID will likely change.
mUns TE is the only Wm6 ROM I have tried which keeps the ID (and I've tried many many).
sickboy555, thanks for your reply.
I *thought* I'd seen something relating to the newer build not changing the ID, but I was obviously mistaken. Like you, I've tried most of the "post Dopod official" Roms and they all change my device ID. I followed the link to the Hermes build and saw that it was a 18125.0.4.2 build, and thought that maybe this would cure it. But obviously not.
What I find funny is that Bepe is building Tomtom in to his builds, and I'd love to use it, except I just upgraded from my SPV M5000 (1 change) and now tomtom won't let me reregister my maps.
Bugger!