Results 1 to 5 of 5
-
26th November 2023, 11:31 AM #1
TomTom Home - End of Life Bypass
Saw some discussions about people looking to purchase maps for NAV2 devices that are deemed end of life by TomTom. I discovered that it's possible to bypass the end-of-life message in TomTom Home and it allows you to purchase maps from the application directly (including the latest v1120 maps).
Requirements:
- This will work on Windows 8 and above without any additional software.
Instructions:
- Make sure to have latest version of TomTom Home installed to avoid any issues (from official TomTom website).
- To use, download the attachment and unzip.
- Then double click "run_me.bat" and it may ask for administrator rights.
- Afterwards, TomTom Home will automatically launch and you can purchase maps freely.
- This process needs to only be done once (unless you update or re-install TT Home), once its been bypassed/patched you can launch TomTom Home normally and bypass will remain.
PS - This assumes TTHome is installed in the default location which is "C:\Program Files\TomTom HOME".
You will also potentially get an offer to update your active map on your device from the main screen for 1 year for a cheaper price. To change the map that is offered, you must switch the active map on the device before plugging into PC.
master131 Reviewed by master131 on . TomTom Home - End of Life Bypass Saw some discussions about people looking to purchase maps for NAV2 devices that are deemed end of life by TomTom. I discovered that it's possible to bypass the end-of-life message in TomTom Home and it allows you to purchase maps from the application directly (including the latest v1120 maps). Requirements: This will work on Windows 8 and above without any additional software. Instructions: Make sure to have latest version of TomTom Home installed to avoid any issues (from Rating: 5Last edited by master131; 26th November 2023 at 06:59 PM.
-
The Following 18 Users Say Thank You to master131 For This Useful Post:
- [ Click To Expand ]
-
beraun (26th November 2023), biggerdave (26th November 2023), birdou (28th November 2023), bondy99 (14th April 2024), bovirus (26th November 2023), dosibox (5th February 2024), fr52 (2nd December 2023), javado (1st March 2024), juanangall (13th June 2024), jungblume2005 (26th November 2023), Kramar (27th November 2023), mace10001 (17th December 2023), pe1agp (26th November 2023), Poteo_Roke (26th November 2023), Proukaet (26th November 2023), Sonaps (26th November 2023), sylpa27 (26th November 2023), XisiX (4th December 2023)
-
26th November 2023, 02:58 PM #2
@master131
In batch file you can use
powershell -ExecutionPolicy Bypass -File "TTHomePatcher.ps1"
or
powershell -ExecutionPolicy Bypass -File "%CD%\TTHomePatcher.ps1"
The PowerShell script .ps1 can converted in an .exe standalone exe file (not reuire PowerShell) using "ps2exe.ps1"
Reference:
-
The Following 5 Users Say Thank You to bovirus For This Useful Post:
- [ Click To Expand ]
-
fr52 (2nd December 2023), pe1agp (26th November 2023), Poteo_Roke (9th January 2024), Sonaps (26th November 2023), sylpa27 (26th November 2023)
-
26th November 2023, 07:08 PM #3
Unfortunately most applications generated from PS2EXE get flagged by anti-virus.
The reason I use %~dp0 is because it means that if the BAT is invoked from command line, you can be in a completely different directory and it will still work as it will look for PS1 file next to the BAT file. See below simulation/example:
Above example, I am currently in J: drive and invoke test.bat located on X: drive. The script is very simple, it states what %~dp0 is and what %CD% and prints it to console. If I use %CD%, it would be looking for the PS1 file on J drive instead of X drive.
-
The Following 4 Users Say Thank You to master131 For This Useful Post:
- [ Click To Expand ]
-
bovirus (27th November 2023), fr52 (2nd December 2023), pe1agp (26th November 2023), Poteo_Roke (9th January 2024)
-
27th November 2023, 02:07 AM #4
@master131
Thanks for very interesting explanation.
-
The Following 1 Users Say Thank You to bovirus For This Useful Post:
- [ Click To Expand ]
-
fr52 (2nd December 2023)
-
2nd December 2023, 07:28 PM #5
@master131
I tried to apply teh patch but in mys system (Windows 10 22H2 64bit) dind't work.ù
Some notes and proposal about Powershells cript.
The TomTom app path could be different in Windows system for 32bit and 64bit and if you update from old TomTom Home version.
Could be
"C:\Program Files\TomTom HOME 2"
"C:\Program Files (x86)\TomTom HOME 2"
"C:\Program Files\TomTom HOME"
"C:\Program Files (x86)\TomTom HOME"
You script seems deisgned for Windows 32bit and TomTom Home not v2.
Please modify the script to check if system is Windows 32bit/64bit and set the program path in right way.
Please check if the TomTom Home path exist and show a warning if the path not exist.
Please add to the end of script a PAUSE that can help user to check if there are error messages or other.
Please take a lookhere
I added to runme.bat a check if process is active and kill it only if is active.
in Powertshell script I added some info reoorpted on the screen about path found for TomTom Home
PowerShell script search TomTom Home path with this order
C:\Program Files\TomTom Home 2
C:\Program Files (x86)\TomTom Home 2
C:\Program Files\TomTom Home
C:\Program Files (x86)\TomTom Home
Thanks.Last edited by bovirus; 3rd December 2023 at 02:58 PM.
-
The Following 4 Users Say Thank You to bovirus For This Useful Post:
- [ Click To Expand ]
-
biggerdave (2nd December 2023), fr52 (2nd December 2023), Poteo_Roke (2nd December 2023), RB261 (4th June 2024)
2023.Q2 Here Australia,New Zealand
Australia New_Zealand HERE 2024.Q2 please