Try to edit the file "reskin" in the the folder "skins".
There are the emulations listed, first entry is a double, replace it with the one for the X30 series for example.
If still no joy, check again if you selected the right version for your device when using the installer.

I spoke to b22222c today and the problem seems to be that all is well but...

ttgo.bif is not created anymore !

After several restarts and reboots it still will not appear.
I know it's strange and I've never seen it before but it seems to be the problem in this case.

I suppose it would be possible to edit the copy from the former backup and fill it with the 9.510 and new map data so that we can trick the device in working about right?

My 5 cents:
A) A clean install on an empty device through TT Home fixes 99% of all possible errors related to a Navcore installation.
This is especially true if the device was formatted correctly - for example by using the format tool from SDCARD.ORG and NOT the Windows Explorer.
B) A ttgo.bif is only created during a succesful boot of the device and for the sake of map activation any ttgo.big from a backup will do as only the Device ID matters for that.

So why not follow basic troubleshooting and do this first

Well... The clean install via TTH was exactly was exactly what I've been trying to do after discovering (much to my surprise!) that no ttgo.bif was being created.
Even then I discovered that ttgo.bif wasn't created and the TT doesn't start up as described.
I was following basic steps.

But, downunder, isn't ttgo.bif also used by TT Home (and Fastactivate) to 'know' which navcore is supposed to be running on the device?
Is a newer navcore not being offered based on that info by TTH?

Not really.
An empty device (no files on it) will be recognised by Home as a device like it came from the factory.
So it will update to a very old Navcore first.
Subsequent updates bring the Navcore numbers up until the latest (official) Navcore is installed.
After each round a boot of the TT is required.
While at it I would also update the bootloader to 5.5112 or 5.5128.
Be aware that before such a "factory rollback" it i highly recommended to use the TT clear flash tool beore starting and again when the final Navcore was updated - run the tool 3 times at start and finnish as recommended by TT.

For the reasons of avaoiding problems Home will never update to the latest Navcore in one go if there is no ttgo.bif file present that informs Home what the currently installed Navcore is.

Hi, i want to thank Razorblatter very very mutch for trying to help. I took the gps to a store and they tell me that the processor was damaged??? Its very strange since the only thing i do was update last software that was available on TTHome, after update say that the gps was going to restart but after that stuck at inicial image...

Thanks for voting for me!

But it is not true that your issue was left unanwered for two days.
In fact both demi gods of this forum (in TT matters) tendriver and downunder tried helping you.
To be frank, it is quite an accomplishments what both gentlemen do without any financial reward for all those people dealing with updates for their devices.

The fact remains that it is no normal matter that ttgo.bif is not created. That does indicate some error within the device.
But on the other hand you stated that it worked if you reinstated the backup (including ttgo.bif).

Although unusual I would think it not impossible that your TT would work if you would create a ttgo.bif manually with the correct data for the navcore (and map). I stated this idea a few days earlier.

A damaged processr is not very likely.
A faulty main board or memory however quite a common thing on these old devices.
Keep in mind the usual lifespan for electronics is around 10 years, after that capacitors will fail, solder connections can be corroded and general wear and tear takes a toll too.
You had bad luck here as the most common sign of hardware failure is the GPS itself lossing function to "see" the satellites.
If you think of getting another one find a GO that is not a 710 or 910 - and at all costs avoid the 630 if you manage to spot one.