Printable View
Anyway your screen is still alive, with the wrong coordinates
I see no other option than trying to find the right place for yes, or .....
This XL has an SD slot, I see a Bootloader 5.5274 ?
If so it must be possisble to put all files on the SD card.
I must have somewhere a manual in Dutch too and I could compare your calib. with mine One XL 89 920 124 864
Afterwards I've seen the differences in both black screens.
But now how to find the spot on yes, I think there is no other option an try and try and try
Someone else with a brilliant idea maybe ?
Give this a try:
If you have reset button:
Turn device on and connect with pc.
When you have the screen "Do you want to connect with pc" push Reset button and wait.
Normally it will connect to pc without asking.
If you don't have reset button.
Turn off device.
Connect with pc.
Push and hold Onn/Off button till you hear the drumms after the green screen is gone.
Wait a moment and see if the device appear in the explorer.
Didn't have to use this method.
For whatever reason it immediately connected to the PC when I plugged in the USB cable just now. Didn't get the "Connect to computer? YES | NO" screen.
Copying my backup back onto my TT XL right now and not going to mess with it anymore.
Well maybe one more time, wanna see what the TT Rider NC looks like.
Use mine, mind your mailbox, please
No succes. After putting back my original files the touchscreen calibration is still messed up.
Trying to correct it now with a cal.txt file.
edit:
And........SUCCES !!!
Created a cal.txt file with some random values I found when I googled "tomtom xl calibration" and now I can tap the intended area on the screen again.
With mine 9.500 ?
I'm sure there is NOT a calib file in mine 9.500
Maybe there is calib in yours and try to use it with 9.500
But I don't see any advantage for your xl, it's a special Navcore for the Rider.
No, with the original files from my backup. There was no calibration file in those either, but with one it finally works again.
But now it's rebooting after selecting a voice on startup...
Only after you select a voice ?
Most of the time they get that same problem when they try to use the same mapsettings.cfg with a new map, which is not always compatible
Removing that file will solve that problem, is that maybe your problem too ?