Live 1535

Joined
Nov 4, 2015
Messages
3
Country
<img src="/styles/default/custom/flags/us.png" alt="United States" /> United States
TomTom Model(s)
TomTom Live 1535
Hello, stumbled upon this forum looking for help with a Live 1535. After installing a map update about 3 weeks ago, my TomTom is now in a cycle of rebooting. It may not happen at the exact same place. Sometimes it is at the opening screen, other times just after the maps pull up.
I have tried a hard reset, even with the gears on the screen, but to no avail.

With MyDrive, I am realizing that there is no way to see files or check for corrupt data.

The last thing I did was add a card to expand memory, ran MyDrive. It moved the maps to the card, but still reboots. Is there something I am missing? Any ideas?
 
I hear 'gears', but let's see if you did the real deed. The screens on your unit may look a bit different, but you'll get the idea.

  1. Make sure that the battery is charged properly by charging the device for at least 2 hours before trying to turn it on. However, do NOT connect the device to your PC until step 5.
  2. Turn on the device with the On/Off button and release it..
  3. Press and hold the On/Off button again until the device reboots (you may see the logo and hear the drums) and continue to hold the button until the bootscreen (black screen with white letters and numbers) is displayed. This takes about 30 seconds. Release the button when you see this screen.
  4. Press and release the On/Off button quickly 3 times in a row.

    Wait a few seconds until the device reboots into recovery mode and displays a grey screen with a spinning cogwheel.

    start_fsck.gif
  5. Connect the device to your computer using the supplied USB cable. Note: As soon as the device is connected to the computer, MyDrive will normally start up automatically, and will download and install the correct software for the connected device, in order to repair the corrupted files.
  6. If MyDrive does not start and you see the following screen, start MyDrive manually.

    wait_for_sa.png
  7. Keep the device connected to your computer until it restarts.

    download_sw_bg.png
  8. Important: The recovery process can take between 5 - 30 minutes, depending on your internet connection. If you disconnect the device from your computer during the recovery process, you might corrupt the device.
  9. When the process is completed, the navigation device restarts and may be disconnected from the computer.
If the software was restored successfully, the device will start as usual without displaying a red cross.
 
There may be a bug with the SD card.
No help but, do you still have one map on internal memory?
If yes, switch to that map then remove the SD card and make a drum roll boot.

If the rebooting cycle has ended then, make a full Windows Explorer FAT32 format of the SD card on your PC.
Next, when you put the card back in the device it will format it to TomTom's system.
Since you own the maps and they are tied in to your eMail address, next time you use MyDrive Connect, all maps will be offered for download again.

Alternatively, wait until the resident Guru 'canderson' reads your post and offers advice.

Oh, and not to forget, a warm welcome to the forum.
 
@Arno
I think he's saying that he added the card after all of this started in an effort to find a solution.
 
canderson I did exactly what your post shows. Made it all of the way thru, it restarted, then I thought I was good to go, only to find it still wanting to reboot on it's own.

And yes, the card was added after the fact. The reasoning was maybe it needed more space, so I put the card in.

With the last map update, it said not enough memory. So I had it only do US instead og all of North America. It installed, fine, but then this reboot thing started up.
 
It's a NAV3 (Miramar) device. I thought it is still the 4 corners.
Pretty sure the newer firmware will work using either method. Sounds like the device responded to it.

@Wingman
Not sure what to tell you. Without access to the file system, it's hard to deal with problems of this sort, but what you've done so far (did it go as described?) should have completely reloaded the firmware. Makes me wonder if you're having hardware issues.
 
Call support for assistance then:

United States
866 486 6866
Monday - Friday: 8:00 a.m. to 8:00 p.m. EDT
Saturday: 9:00 a.m. to 6:00 p.m. EDT
 
Interesting update. After going thru the above procedure for the fifth time, last night. It started working again. I left it on all day in my truck, just to see if it would stay on. It did and worked perfectly. Not sure what is up, but happy to have it working again. Thanks everyone!
 
That's good news. Can you say specifically if things went (when they went) as noted above. What was different the last time, if anything?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Latest resources

Forum statistics

Threads
29,340
Messages
198,652
Members
68,531
Latest member
hussa

Latest Threads

Back
Top