Related
I want to upgrade my XDA2 to a IIs but I don't know whether TomTom will let me do this without buying another copy of the TT software. Has anyone done this before? Would I have to send all my TT CDs back to TT to get them swapped for new, unregistered ones?
As far as I know, my copy of TT (and all the maps I've bought) is registered to my specific XDA2 so it couldn't be re-installed on any new machine that I bought.
Thanks in advance.
PS. What would happen if I lost this XDA2 and got a replacement? Same situation, I guess.
For TomTom 3, you can install to a second alternative device after 7 days has passed from initial install and then a 3rd after 6 months.
So if you have only ever installed to the one device and 7 days has passed you won't have any problem.
You can of course re-install to the same hardware as many times as you wish without affecting the install count.
If you had your hardware stolen or replaced under warranty then TomTom will re-issue a new key if you can provide documentary proof that the hardware was replaced etc.
Having said all that, CeBit starts next week and there 'may' be some news on the TomTom front Registered owners of current versions may want to watch our site for news from Mar 10th.
Thanks for your reply, Darren. I bought TT3 itself from PCWorld so that's no problem. The additional European maps my Dad gave me - he bought them off some dodgy geezer on eBay. All original but seal broken. I guess this geezer will have installed them at least once, knowing that 7 days later I'd be able to install them on another machine and all would be happy. :scratchchin: Let's hope he doesn't install them on another machine in 6 months' time. Best I upgrade my phone nice and quickly! My wife will be pleased... NOT! :roll: :lol:
It is because of tomtom and their stringent rules that keygens have been created to overcome this problem, why should you be restricted to one or two changes of phone/pda once you have bought the software? I have a genuine copy of tomtom but I use a keygen to get new codes each time I change phones/pda's, otherwise I wouldnt be able to use legitimate software as I need and it saves me having to go through the process of contacting tomtom and being told I cant have another code for 6 months.
Changing units
Hi guys,
I've just done over 8 weeks in 19 countries without my TT BT Nav3 & TT traffic because O2 replaced my unit (because it wouldn't work with TT) unfortunately they classed it as stolen :?: & gave it a new ID, (in any case I have since read in forums that the problem was caused by Chinese made 1gb SD cards :evil: which won't run with TT and freeze everything!)
Decided to wait until I got home, upgraded to an XDA IIi, but, I've tried several uninstall & re-installs but each time it says 'You have not downloaded voice files, so your TT will not work properly'
I now have FOUR 1gb SD cards (bought from aria.com) which seem ok for anything else but no good with TT, Ye Gods!!!!
After problem after problem with TomTom I hope they sort all this out with TT 5!
Who knows, maybe they'll even manage their maps down from the extremely annoying 9 unmarked disks, OOPS! there goes another pig flying over :wink:
hey all, my XDA II O2 is dead, i have a bit of a story to tell about it too. the poor thing won't boot up past the O2 spash screen.
i was initially selling my O2 around the traps as a working unit, then someone asked me to show them landscape view, and i didn't know how. i soon found out i needed to upgrade to 2003se or 2005. so on my homage to flashing my O2's ROM. i went and tried a 2005 and some random version radio stack hoping to upgrade two things at once, then, only one worked. my OS flash was fine, but my radio ROM didn't work at all. so basically i could get into WM2003, 2003SE, 2005 fine but couldnt use my simcard.
i've tried countless times to manually fix it aswell as using the official O2 ROM update off their site. then i went and sent it to O2 customer service or whatever it's called this year . they charged me $45AUD for general service fee which included flashing the radio and OS roms up to the latest. then they ring me up one morning saying my poor O2 needs a new motherboard (somewhere between $350 - 450 i think). i asked why, they said because it wouldn't power on at all. so i tried turning it on, it didnt work all of a sudden, so to speak.
i still had to pay the $45aud and ended up without a working O2, at all.
i felt furious but helpless and tried not to have to pay the fee, but had to.
long story short, heh, i need to do something with my shell of a XDA II, either sell, sell parts, fix, find a special ROM flash that might fix it. i don't know, i've tried so hard and have gotten nowhere. so, guys, any insight in what i could/should do?? any help would be greatly appreciated. thanks! :shock:
OH OH OH also, on that note, i can't go into bootloader mode or any other mode at all, so i cant re-flash
Threaten to sue. It worked partially when you sent it to them as it would power up - they've made it worse.
Richard
hey, thanks for the reply..
i've left it too long, i got so discouraged from touching it after getting it back.
i will ring them up/ get their details on who to ...ring next, i guess.
thanks!
damnation said:
hey, thanks for the reply..
i've left it too long, i got so discouraged from touching it after getting it back.
i will ring them up/ get their details on who to ...ring next, i guess.
thanks!
Click to expand...
Click to collapse
If all else fails I can sell you a working mainboard for a LOT less than $400 aus but I would need to know which LCD type you have.
Richard
Threaten to have a ghay german cannibal come knocking jk
Hello Universalowners!
I got a really big Problem. My Universal falled down 4 month ago. Because of that the USB-Connector broke out. Till yesterday that was no problem. My Universal worked pretty good. Under Windows, I was able to connect to my device by Bluetooth.
No here comes my problem.
Yesterday I booted up my device and I dont know why, it came up in bootloader mode.
I tried every key combination, but it does not reboot back to windows. Even Both softkey+reset does not work.
My friend owns an universal too, and we tried to back up his rom to sd card with mtty. The d2s command is locked on his device. There is no chance to backup his rom to sd card.
That would be my only chance to get my universal back to life.
The change of the usb connector would cost me a lot Euros.
I really don´t need the usb connection if I have a running system.
I charge my batteries by an external device and everything else I can do by bluetooth or infrared.
So please tell me, what I can do, to get my problem solved. I heared something about the tool itsutils.exe with rapi enabler on my friends device. But I really do not know, how I have to handle this.
Could someone send me the image, which I can write to sdcard with my laptop?? Please help me. I need my universal like the air to live!
Hope I will get a soon answer from you!! Thank you in advance!!!!!!
Don't o2 Germany do an insurance plan like o2 UK?
If I were you I'd buy the connector for the Euro or so it will cost, and solder it in myself. But of course, if it goes wrong you'll have fried your XDA with no backup. Can't you just call o2, take out insurance, then about a month later, "Lose" it?
Hello all! I have a sad story and an opportunity.
Sad story: I forgot my Universal on top of my car today and when I came around a bend in the road, it was slung out into a highway. The first car dodged it, and the second car aimed for it. I have taken pics. I think ti would have survived the slinging, and I am testing to see if the mainboard survived being ran over.
Opportunity: I'd like to get a new one. I don't mind parts-ing one together either. I am comfortable buying on eBay, and I don't mind it if I have to pay for international shipping, but I'd prefer to buy from the US for quicker delivery time.
I was just about to start really customizing the ROMS and all that too....
Sigh.
I hafe attached pics of the carnage. The microSD card survived. I did pull all of my data off though. Luckily I had done a hard reset las week, so I had all my numbers backed up. The SIM card survived as well, and I am borrowing a phone I gave a firend for the time being.
Wow those are some scarey images! Sorry for your loss, but that needs to be a closed casket funeral...
I've been considering selling my Uni/JasJar, PM me if you're interested in buying a used device with a bit of wear.
Oh my god............
RIP Uni are you trying to disassemble it for some pics of motherboard?
It looks better than I would have thought after being run over. You may be lucky and Mobo may be ok. You can buy replacement screens and casings.
Was it a compact that ran it over ? Cause I really cant see the Uni being that strong?
There are quite a few Uni's going on the UK Ebay anywhere from $200 USD to $80 USD if you are patient enough.
Good luck with finding another!
2 minutes silence for the Uni please......
Status update
I have purchased a B stock unit from eXpansys (the last one they had) for a decent price. Only problem is with the new unit, all I can do is get into the boot loader to see that it is version 1.00, and give it the hard reboot command. The unit appears to respond to the command but does not initiate the hard reset.
Hard reboot command I used: two soft buttons and the reset button.
Bootloader command I used: power, brightness, and reset button.
The bootloader does recognize that the difference between a USB and !USB connection. However, Windows consistently reports that the USB device has malfunctioned.
At first I thought it was a battery issue because the unit looks like it is brand new. So I waited patiently until I got home and tried all of the batteries I have here at the house. Yes, I was wary sticking the battery that was in the unit that was ran over into it, but I did try it. I have tried 3 chargers and two computers, and NADA. The only response I get from the device is using one of the two commands above.
Other random observations:
I tried inserting an old (disconnected but good) SIM card into it. Nada.
The battery was shipped in the battery compartment.
The backlight does work, as does the screen to some degree.
When I first plugged it into the charger, the battery status LED was red, as I anticipated.
The battery status indicator no longer turns red when the unit is plugged in. It does turn red when the battery is removed and power is applied.
Postulations at this point:
I wonder if I could load a ROM image to it?
I wonder if the battery is really charged.
Any and all help will be much appreciated on the matter.
disection
Win_XP said:
RIP Uni are you trying to disassemble it for some pics of motherboard?
Click to expand...
Click to collapse
I have disassembled it already and done some preliminary testing. The power LED does illuminate RED. I have tried attaching a battery and holding it, but hats not producing anything. But then again the screen is cracked like its cool, so I don't know what to expect.
I'll post pics when I get a chance.
beast0898 said:
Was it a compact that ran it over ? Cause I really cant see the Uni being that strong?
There are quite a few Uni's going on the UK Ebay anywhere from $200 USD to $80 USD if you are patient enough.
Good luck with finding another!
Click to expand...
Click to collapse
It was one of those KIA/Mercades/lexus lifted CAR SUV things. They AIMED for it.
I looked on ebay, but I never though to check the UK side. Usually eBay does that for em for some reason....
Situation update
I have had a couple of offers and much sympathy. Thanks!
My unit from expansys is up and running. I was up till 3 am saturday morning playing around with it. I stumbled across a few posts that gave instructions on how to deal with a potentially bricked device. As far as I can figure. my phone was shipped to me without an OS. I knew that PCs could do that, but can you just blank the OS on a phone? I can theoretically see how that might be possible, but why would that happen? Do they not get shipped out with OS's? that baffles me.
The specific process of deduction I used:
read the manual (the service manual from HTC). It said to either reload the ROM or the mobo was defective. I started looking on this forum for the procedures and files neccessary.
It seemed that my phone was not booting, so I looked into the ROM upgradeing/reflashing pages.
Links to pages I found useful:
http://forum.xda-developers.com/announcement.php?f=357
http://forum.xda-developers.com/showthread.php?t=367448
http://wiki.xda-developers.com/
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
http://wiki.xda-developers.com/index.php?pagename=Flashing Guide
http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade
http://wiki.xda-developers.com/inde...consumption measurements of the HTC Universal
http://wiki.xda-developers.com/inde...y car or USB charger! It just doesn't charge!
http://forum.xda-developers.com/showthread.php?t=298613
http://forum.xda-developers.com/showthread.php?t=285435
As you can see, the wiki was quite helpful for me. Thae list above is not inclusive. I thought I had bookmarked all the pages I found helpful, but it did not apepar to be so. I have done much reading on this forum, and I purchased my original Universal over a year ago. I say that to let any newbies know that this is not a simple process and should not be attempted until you have a clear picture of what's going on.
I also tried the set 0 14 procedure, but that sis NOT work in my case.
What finally got me was the imate ROM I have attached to this page. It was able to see my universal, but only when I was in the bootloader. I will say that again because it bears repeating. I put the phone into the bootloader and ONLY THEN could I update the ROM on the device. I found no instructions anywhere on this, I had to figure it out on my own. The way I discovered it though is kinda neat. When I just plugged the phone into my computer, windows would not recognize it and say that it malfunctioned. If I plugged it into my computer with it in the bootloader, I got that nice sound that windows makes when new hardware is found. Also, I tried the Universal RUU and it did not recognize that the phone was attached in either way. Lastly, I first tried the ROM update with the phone not int he bootloader, and the IMATE program didn't see the phone. I tried it with it in the bootloader, and it did its thing.
I have attached a few of the files I found useful. I found these on this site, in some posts.
This is not a formal writeup, so please forgive any grammatical errors or rambling. I just wanted to share what I found.
So I finally just switched the SIM card back into the new phone. I tried to get MMS going, and SAME FRAKKIN thing: small pics. ARGH!!
AllanonMage said:
I have had a couple of offers and much sympathy. Thanks!
My unit from expansys is up and running. I was up till 3 am saturday morning playing around with it. I stumbled across a few posts that gave instructions on how to deal with a potentially bricked device. As far as I can figure. my phone was shipped to me without an OS. I knew that PCs could do that, but can you just blank the OS on a phone? I can theoretically see how that might be possible, but why would that happen? Do they not get shipped out with OS's? that baffles me.
The specific process of deduction I used:
read the manual (the service manual from HTC). It said to either reload the ROM or the mobo was defective. I started looking on this forum for the procedures and files neccessary.
It seemed that my phone was not booting, so I looked into the ROM upgradeing/reflashing pages.
Links to pages I found useful:
http://forum.xda-developers.com/announcement.php?f=357
http://forum.xda-developers.com/showthread.php?t=367448
http://wiki.xda-developers.com/
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
http://wiki.xda-developers.com/index.php?pagename=Flashing Guide
http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade
http://wiki.xda-developers.com/inde...consumption measurements of the HTC Universal
http://wiki.xda-developers.com/inde...y car or USB charger! It just doesn't charge!
http://forum.xda-developers.com/showthread.php?t=298613
http://forum.xda-developers.com/showthread.php?t=285435
As you can see, the wiki was quite helpful for me. Thae list above is not inclusive. I thought I had bookmarked all the pages I found helpful, but it did not apepar to be so. I have done much reading on this forum, and I purchased my original Universal over a year ago. I say that to let any newbies know that this is not a simple process and should not be attempted until you have a clear picture of what's going on.
I also tried the set 0 14 procedure, but that sis NOT work in my case.
What finally got me was the imate ROM I have attached to this page. It was able to see my universal, but only when I was in the bootloader. I will say that again because it bears repeating. I put the phone into the bootloader and ONLY THEN could I update the ROM on the device. I found no instructions anywhere on this, I had to figure it out on my own. The way I discovered it though is kinda neat. When I just plugged the phone into my computer, windows would not recognize it and say that it malfunctioned. If I plugged it into my computer with it in the bootloader, I got that nice sound that windows makes when new hardware is found. Also, I tried the Universal RUU and it did not recognize that the phone was attached in either way. Lastly, I first tried the ROM update with the phone not int he bootloader, and the IMATE program didn't see the phone. I tried it with it in the bootloader, and it did its thing.
I have attached a few of the files I found useful. I found these on this site, in some posts.
This is not a formal writeup, so please forgive any grammatical errors or rambling. I just wanted to share what I found.
So I finally just switched the SIM card back into the new phone. I tried to get MMS going, and SAME FRAKKIN thing: small pics. ARGH!!
Click to expand...
Click to collapse
Hi,
Some of the commands for MTTY are not in the standard bootloader command list, best advice is to supercid your device (this will help in recovery if things go wrong later too) then once supercid is complete, upgrade the Bootloader version and flash a complete Rom to the device, radio, extended and OS in one flash.
All info is in the Wiki mate, if you need any further help, post back to us or PM me.
Glad you got a device back up and running, ca'nt you sue the guy for intentionally hitting your old one................LoL!
Cheers,
Beasty
why my dopod 838pro sometime it cannot detect a radio rom and show a NO GSM, but if detect it a radio rom and it will hang about and half hours and reset will turn back to NO GSM, is hardware or software prob, anyone can give me a solution?
Provide more information - OS version and Radio version. Its probably a hardware problem but you may try to reflash to a manufacturer's shipped version and retest.
I had the same problem basically. Phone would freeze up, get repeated NO GSM messages, drop the radio even when it finds it after several minutes of use. I did buy the phone off eBay used and it did freezeup in WM5 ALOT.
I took the phone apart and cleaned all the contacts - same problems. Reflashed manufacturer's rom again and it took. Before it sometimes would hang up - looking for GSM radio. Took it apart again FULLY and put everything back together. It is now working for the past week. No freezeups or drops. Seems to always find GSM on bootup.
last time using a official rom wm6 also freeze up, then flash it to manila2d rom, it also got a same prob, try reflash a radio rom, but always get stuck at 6%, but try and try then 100% done, but also same prob.
so ur solution is try Reflashed manufacturer's rom again?
Thats what I did but the flash alone didn't fix the problem. I don't think a rom flash will bring your phone back but you may get lucky. I had to open it up and clean and reposition things. For some reason it worked. I still get screen fade to white and the directional pad on the front sometimes doesn't work - you move the scroll wheel and it will work again. Might have to replace the dPad circuit board or flex cable. The HERMES seems to have MAJOR problems with quality control and the radios. I personally think the battery presses against a backing plate which rests directly against the chipsets. The silver plate behind the battery does flex and it shouldn't. It probably should be a little thicker to prevent flexing. The heat from charging and the pressure from the battery I think causes the radios to fail. Bad soldering also may be a problem but any pressure on a motherboard and chipsets isn't a good thing. Also screws that are too tight also may contribute to the problem.
My phone has been working for about a week. Prior to that it was getting constant NO GSM errors on bootup and dropped calls. Today the phone was out of the house for the first time in weeks and it worked without any problems - no freezes (did a lot before) and no dropped radio. It has been sitting on my desk for two weeks without any problem. Will try it a few more days and see.
herm200 no GSM
Hi! I have read all thread about no GSM from here.
I have already do many many tests, tried to flash any radio rom extracted, hard reset, mtty with set 1e 1... I have already dissasemble and reassemble it
but no one fix the problem No GSM.
I have the same probleme, sometime no gsm and sometime ok.
So please, if anyone find everything which can fix this problem please post it!
Sorry for my english!
Thanks a lot for all jobs and helps.
Hello all, my hermes had this problem too!
Sometime it works, " 1.56.70.11" and sometime no! "NO GSM"
i have done about twenty flash thinking it will resolve this problem...
After reading a topic on this problem, i have understand it was an hardware problem. Something unsolde.
I have buy "double face scotch", i have disasemble the phone completely.
And on every chip and on the "battery"( little round and flat) i have put a little piece of scotch. it will do a pression on every chip to keep chip connected on the motherboard.
From this moment, the phone has never freeze, no more "no gsm" message!
ALL IS GOOD
Sorry for my poor english.
Many things can affect the radio
Try this...
Un plug your batt... insert a big piece of aluminium under the batt over the gsm chip... it wil not work properly... Magnetic issues... the batt do this things too i prove it on a Nokia... the batt without the stick = radio problem no signal...
Abd here i got the same trouble no gsm sometimes i realized that has been a lot flashes but noup, was a dialer that makes this issues 3G phone canvas,.... back to touch dialer 3G or 2G and its good now... think the CPROG and some other is not so compatible.
Desperately please help me, my Dopod 838 Pro has No GSM!
hey dude try another rom... the roms with HTC phonecanvas 2g or 3g do this issues on my hermes dunno why... thats th reason i dont cook anymore phoncanvas on my roms.
Update Radio ROM to 1.47
I had same problem just recently, and the recommendation that I got was update your Radio ROM ONLY...I upgrade to Radio 1.47 as all the time I was loosing service connection as well as No GSM...after this, my Hermes took live again.
I had 1.16 Radio...!!! and that issue came up after upgrading to one of the so many cooked ROM...I don't remember which one...
Check this link for more info, it saved my life!!!
http://forum.xda-developers.com/showthread.php?t=295751
Cheers,