TomTom Start 60 broken flash   

Post a reply

TomTom Start 60 broken flash

Postby mystical » Sun Jan 10, 2021 5:35 pm

Hi, I have a TomTom Start 40.
I updated it to the latest version, but it crashed a few days later. After switching on, it remained on the logo.
I changed the emmc flash, but the data in
3: rescue
4: content
partitions is damaged.

Does anyone have a dump for this navigation?

[Please Register or Login to download file]

How can I decrypt the .ttpkg package? The information I need is inside. I have uImage, but rootfs.img is corrupted.

Partition map:
1:uboot
2:fdt
3:rescue
4:content

Code: Select all
fdisk -l /dev/sdc
Disk /dev/sdc: 29.1 GiB, 31268536320 bytes, 61071360 sectors
Disk model: Card  Reader   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x7e1e8ffe

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdc1  *      256     1791     1536  768K da Non-FS data
/dev/sdc2        1792     2047      256  128K da Non-FS data
/dev/sdc3        2048    67583    65536   32M 83 Linux
/dev/sdc4       73728 61071359 60997632 29.1G 83 Linux


[ID]
LocalID = ['N4Start_4_noBT_8192', 'N4Start_4_TMC_8192', 'N4Start_6_TMC_8192', 'N4Start_6_noBT_8192', 'N4Start_5_TMC_8192', 'N4Start_5_noBT_8192']-13.057.1607767.2099-7FD.14Q02.002.00.3-NAV4_START_EU_(ALL_TTS)_8GB_v3.EXT3
imageID = Europe-933.5663

[Image information]
Birthday = Wednesday 25 June 2014, 15:59:52
Image type = EXT3 8GB
Item number = 7FD.14Q02.002.00.3
Item description = NAV4 START EU (ALL TTS) 8GB v3
Changelist = 1608536
Application version = 13.057
Application build = 1607767.2099
Map 1 name = Europe
Map 1 version = 933
Map 1 build = 5663
Last edited by mystical on Mon Feb 15, 2021 6:03 am, edited 1 time in total.
mystical offline

Junior Member



 
Joined: Sun Jan 10, 2021 2:14 pm
Posts: 4
Has thanked: 0 time
Been thanked: 1 time
Top

Share On:

Share on Facebook Facebook Share on Twitter Twitter Share on Digg Digg Share on Reddit Reddit Share on Delicious Delicious Share on Tumblr TumblrShare on Google+ Google+Share on MySpace MySpace

Re: TomTom Start 60 broken flash

Postby fredderf » Mon Jan 11, 2021 1:03 pm

No, we can't help with a NAV4 device...maybe in the future though

The other alternative would be to contact TomTom direct to see if they can help as I bet you're not the only one to have experienced this problem
fredderf offline

Administrator



 
Joined: Sun Nov 17, 2013 2:23 pm
Posts: 3066
Location: UK
Has thanked: 622 times
Been thanked: 3757 times
Top

Re: TomTom Start 60 broken flash

Postby mystical » Mon Jan 11, 2021 5:52 pm

I contacted the support, I hope they give me the necessary files to restore the device.

Nothing will happen to the support. It's like talking on the wall.

Interesting log:
<5>[ 0.000000] Linux version 3.2.0-p4-1607671 (svc_quickbuild@nlsrvup-qbs07) (gcc version 4.7.2 20120910 (prerelease) (Linaro GCC 4.7-2012.09) ) #2 Tue Jun 24 18:20:24 CEST 2014
<4>[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
<4>[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
<6>[ 0.000000] Machine: TomTom AM335X PND, model: nav4-b4
<4>[ 0.000000] Memory policy: ECC disabled, Data cache writeback
<7>[ 0.000000] On node 0 totalpages: 130816
<7>[ 0.000000] free_area_init_node: node 0, pgdat c06af450, node_mem_map c0a2c000
<7>[ 0.000000] Normal zone: 1024 pages used for memmap
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 129792 pages, LIFO batch:31
<6>[ 0.000000] AM335X ES2.0 (sgx neon )
<7>[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
<7>[ 0.000000] pcpu-alloc: [0] 0
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129792
<5>[ 0.000000] Kernel command line: console=ttyO0,115200n8 sysboot_mode=warm coldstart_source=unknown androidboot.console=ttyO0 androidboot.bootloader=2011.09-p4-1581104 consoleblank=0 lpj=2988032 fbmem=0x7f800@0x9fd62708 quiet mmc_dev=1 revocation_count=0 secbootctx=9ffff000
<6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>[ 0.000000] Memory: 510MB 1MB = 511MB total
<5>[ 0.000000] Memory: 507740k/507740k available, 16548k reserved, 0K highmem
<5>[ 0.000000] Virtual kernel memory layout:
<5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
<5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
<5>[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)
<5>[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
<5>[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
<5>[ 0.000000] .text : 0xc0008000 - 0xc05be000 (5848 kB)
<5>[ 0.000000] .init : 0xc05be000 - 0xc069b000 ( 884 kB)
<5>[ 0.000000] .data : 0xc069c000 - 0xc06b1448 ( 86 kB)
<5>[ 0.000000] .bss : 0xc070f2b0 - 0xc0a2b1e0 (3184 kB)
<6>[ 0.000000] NR_IRQS:396
Last edited by mystical on Mon Feb 15, 2021 6:05 am, edited 1 time in total.
mystical offline

Junior Member



 
Joined: Sun Jan 10, 2021 2:14 pm
Posts: 4
Has thanked: 0 time
Been thanked: 1 time
Top

Re: TomTom Start 60 broken flash

Postby mystical » Tue Jan 12, 2021 6:45 pm

How to make a dump from a broken flash

1. You need skills and appropriate equipment for desoldering and soldering flash memory.
[Please Register or Login to download file] - I use these adapters for reading and writing.

2. Create a dump under Linux

Code: Select all
dd if=/dev/sdc of=tomtom-nav4-full_dump-BROKEN_bs512.bin

Take your time and use 512 bytes per second, which is the default.

Unplug the original flash memory and insert the adapter with a working emmc flash.
I used SDIN9DW4 32G SanDisk eMMC.
I lost a lot of time with THGBMFG8C4LBAIR 32G Toshiba eMMC, with it the navigation does not boot.
Code: Select all
dd if=tomtom-nav4-full_dump-BROKEN_bs512.bin of=/dev/sdc
e2fsck -p /dev/sdc3
e2fsck -p /dev/sdc4

fdisk /dev/sdc

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): a
Partition number (1-4, default 4): 1

The bootable flag on partition 1 is enabled now.

Command (m for help): w
The partition table has been altered.
Syncing disks.

fdisk -l /dev/sdc
Disk /dev/sdc: 29.1 GiB, 31268536320 bytes, 61071360 sectors
Disk model: Card  Reader   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start      End  Sectors  Size Id Type
/dev/sdc1  *      256     1791     1536  768K da Non-FS data
/dev/sdc2        1792     2047      256  128K da Non-FS data
/dev/sdc3        2048    67583    65536   32M 83 Linux
/dev/sdc4       73728 15269887 15196160  7.3G 83 Linux

I have two hard drives, the first is sda and the second is sdb. For this reason, in my case the usb adapters are sdc, sdd. You may have sdb.

If you are lucky you already have a working emmc flash. Check if you can mount both partitions. Check the sha1sum values.
These are from 00000000-0311-0020-1000-69f2778f0001_system-update.ttpkg
083ee304f7730f7af658a275f49d6b26841fa80f system-update_20.100.0001.311_all_data/uImage
ab424bbf31807b580e290178f1c1b855a485e996 system-update_20.100.0001.311_all_data/rootfs.img.new


Code: Select all
sha1sum /media/mystical/7037594c-f1b9-4c09-b990-3d76c85f19b0/uImage
083ee304f7730f7af658a275f49d6b26841fa80f  /media/mystical/7037594c-f1b9-4c09-b990-3d76c85f19b0/uImage
sha1sum /media/mystical/7037594c-f1b9-4c09-b990-3d76c85f19b0/rootfs.img
88163a071671ca80d81e543cb8359c06b0ec14f6  /media/mystical/7037594c-f1b9-4c09-b990-3d76c85f19b0/rootfs.img

In my case, rootfs.img is corrupted.

Try mounting rootfs.img
Code: Select all
mount -o loop /media/mystical/7037594c-f1b9-4c09-b990-3d76c85f19b0/rootfs.img /mnt

Compare uboot
vbindiff /dev/sdc1 /mnt/etc/firmware/bootfs.img

Compare s/n - license key
vbindiff /dev/sdc2 /media/mystical/7037594c-f1b9-4c09-b990-3d76c85f19b0/fdt.bin


fdt.bin and /dev/sdc2 contain information about s/n - license key, make backup and do not share it.

If you want to share a full backup:
Code: Select all
dd if=/dev/sdc2 of=sdc2
dd if=/dev/zero of=/dev/sdc2

Move fdt.bin to your computer.
dd if=/dev/sdc of=tomtom-nav4-full_dump_bs512.bin count=15269887

Recovery s/n - license key
dd if=sdc2 of=/dev/sdc2
If there is a problem with the serial number, the navigation starts in rescue mode.

Recovery uboot
dd if=/dev/sdc1 of=sdc1
dd if=/dev/zero of=/dev/sdc1
dd if=/mnt/etc/firmware/bootfs.img of=/dev/sdc1
mystical offline

Junior Member



 
Joined: Sun Jan 10, 2021 2:14 pm
Posts: 4
Has thanked: 0 time
Been thanked: 1 time
Top

Re: TomTom Start 60 broken flash

Postby mystical » Mon Feb 15, 2021 6:18 am

[Please Register or Login to download file]

1. Follow the above guide first.

2. Using tomtom-nav4-dump-bs512.bin for unbrick:

Code: Select all
dd if=tomtom-nav4-dump-bs512.bin of=/dev/sdc
dd if=sdc2 of=/dev/sdc2


If there is a problem with the serial number, the navigation starts in rescue mode.
Copy fdt.bin to content partition.

data/ttcontent/common/installed/TomTom-Cfg/release.nfo
TomTom-Cfg/.ttcs.nfo

Copy your files or manually edit the above files.

NB: If you use emmc larger than 8G, you can increase the partition size with GParted.

Before soldering the flash, check the sha1 sum on rootfs.img
This is the correct sum.
ab424bbf31807b580e290178f1c1b855a485e996 rootfs.img


If sha1 sum is different:
Code: Select all
rm /sdc4-content_mount_dir/rootfs.img
mount -o loop,offset=37748736 tomtom-nav4-dump-bs512.bin /mnt/
sha1sum /mnt/rootfs.img
cp /mnt/rootfs.img /sdc4-content_mount_dir
mystical offline

Junior Member



 
Joined: Sun Jan 10, 2021 2:14 pm
Posts: 4
Has thanked: 0 time
Been thanked: 1 time
Top

Re: TomTom Start 60 broken flash

Postby lamedia » Sat Dec 18, 2021 5:51 pm

Hi, I accidentally restored a TomTom Go 50 with the backup from another TomTom Go 50. Now it doesn't start. What can I do?
lamedia offline

Junior Member



 
Joined: Mon Feb 15, 2016 5:08 am
Posts: 1
Has thanked: 0 time
Been thanked: 0 time
Top
Post a reply

Return to Tutorials

 


  • Related topics
    Replies
    Views
    Last post

Who is online

Users browsing this forum: No registered users and 2 guests

Switch to mobile style
Powered by phpBB® Forum Software © phpBB Group
phpBB SEO
Design: NaviTotal.com © 2015


NaviTotal.com tested by Norton Internet Security NaviTotal.com tested by McAfee Internet Security