Results 21 to 30 of 127
-
13th September 2021, 07:41 PM #21
GO Discover i think is not Nav5 but maybe we can call it Nav6 !
tomtom go discover has his twin on truck device ... it's Go Expert
must ask to team MSTMS about your tomtom Go Discover, but i think it's not Nav5 ...it's newes model ....sure i can wrong so we must wait for MSTMS team answer .....
-
20th November 2021, 06:25 PM #22
Hi.
I have error messages on a backup that I'm doing. red line
Is it normal
GO 6200
Please check the device manager and look for QLoader 9008 COM Port
Enter the COM port number: COM17
Version 2.15
Downloading flash programmer: flash_programmer.bin
Successfully open flash programmer to write: flash_programmer.bin
Waiting for flash programmer to boot
Dumping data to file fdt_20211120130602.bin
Dumping at start sector: 0 for sectors: 0 to file: fdt_20211120130602.bin
Programming device using SECTOR_SIZE=512
<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="1048576"/></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="logbuf@0x08057C98 fh@0x08054B00" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="1048576" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8909" /></data>
Using 99 bytes from mbuffer
<?xml version="1.0" encoding="UTF-8" ?><data><log value="logbuf@0x08057C98 fh@0x08054B00" /></data>me="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="1048576" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8909" /></data>
Connected to flash programmer, starting dump
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="1" physical_partition_number="0" start_sector="1"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 1
Downloaded raw image at speed 512 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 1" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="32" physical_partition_number="0" start_sector="2"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 32
Downloaded raw image at speed 16384 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 1" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="2048" physical_partition_number="0" start_sector="207872"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
hRead = INVALID_HANDLE_VALUE, zeroing input buffer
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 1" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
Status: 0 (null)
Version 2.15
PblHack: Error - 1836597052
Did not receive Sahara hello packet from device
!!!!!!!! WARNING: Flash programmer failed to load trying to continue !!!!!!!!!
Dumping data to file userdata_20211120130602.bin
Dumping at start sector: 0 for sectors: 0 to file: userdata_20211120130602.bin
.0" encoding="UTF-8" ?><data><log value="XML (0 bytes) not validated" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" /></data>
Programming device using SECTOR_SIZE=512
<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="0" SkipWrite="0" MaxPayloadSizeToTargetInBytes="1048576"/></data>
<?xml version="1.0" encoding="UTF-8" ?><data><log value="logbuf@0x08057C98 fh@0x08054B00" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="1048576" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8909" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" MinVersionSupported="1" MemoryName="eMMC" MaxPayloadSizeFromTargetInBytes="4096" MaxPayloadSizeToTargetInBytes="1048576" MaxPayloadSizeToTargetInBytesSupported="1048576" MaxXMLSizeInBytes="4096" Version="1" TargetName="8909" /></data>
Connected to flash programmer, starting dump
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="1" physical_partition_number="0" start_sector="1"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 1
Downloaded raw image at speed 512 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 1" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="32" physical_partition_number="0" start_sector="2"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
Sectors remaining 32
Downloaded raw image at speed 16384 KB/s
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 1" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
<?xml version="1.0" ?><data>
<read SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="29871686" physical_partition_number="0" start_sector="663960"/>
</data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data>
hRead = INVALID_HANDLE_VALUE, zeroing input buffer
<?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 1" /></data>
<?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="false" /></data>
Status: 0 (null)
Appuyez sur une touche pour continuer...
Thanks for your help.Last edited by yopy; 20th November 2021 at 07:09 PM. Reason: Adds remnants of backup messages
-
20th November 2021, 10:40 PM #23
──(kali㉿kali)-[~/Desktop/TTNav5/2_Linux]
└─$ sudo su
[sudo] password for kali:
┌──(rootkali)-[/home/kali/Desktop/TTNav5/2_Linux]
└─# chmod +x ./patch_nav5.sh
┌──(rootkali)-[/home/kali/Desktop/TTNav5/2_Linux]
└─# ./patch_nav5.sh
This script will install the mstms Nav5 patch on device /dev/sdc
PLEASE BE SURE YOU HAVE A BACKUP OF USERDATA PARTITION ~14GB !
Press 'y' + enter to continue
Press any other key + enter to exit
y
Mounting /dev/sdc
Mounting OK, installing files...
Files installed, umount /dev/sdc
Checking /dev/sdc for filesystem errors and automatic repair (Tomtom doesn't do this !)
e2fsck 1.46.4 (18-Aug-2021)
/dev/sdc is mounted.
e2fsck: Cannot continue, aborting.
Done, enjoy !
┌──(rootkali)-[/home/kali/Desktop/TTNav5/2_Linux]
└─#
I didn't succeed. I don't know what's wrong
-
20th November 2021, 11:00 PM #24
When put it in EDL mode, in Device Manager, do you see that in Puerto COM it has 17?
When he made backup, he says he gave errors?
how much does it weigh? fdt_20211120130602.bin.
how much does it weigh? userdata_20211120130602.bin.
When you put patch with Kali also error, to verify that it is in /dev/sdc write in terminal this command; fdisk -l.
You can put a photo of what I have asked.
regards
-
The Following 1 Users Say Thank You to simba For This Useful Post:
- [ Click To Expand ]
-
yopy (22nd November 2021)
-
21st November 2021, 04:09 AM #25
simba:When put it in EDL mode, in Device Manager, do you see that in Puerto COM it has 17?
Yes Simba, I checked well, the port number was well 17
simba:When he made backup, he says he gave errors?
how much does it weigh? fdt_20211120130602.bin.
how much does it weigh? userdata_20211120130602.bin
For errors. everything I copied pasted into my first post.
For the time that it lasted, I can not confirm it because I did not always stay in front of the monitor.
simba: When you put patch with Kali also error, to verify that it is in /dev/sdc write in terminal this command; fdisk -l.
You can put a photo of what I have asked.
Yes I checked well with the "fdisk -l" command that the disk name was well "sdc". So nothing to edit. I leave them as it is.
Sorry for my English. I use Google Translation to communicate with you. Thank you for wanting to help me.
Tomorrow I will try another time. I will also post pictures.Last edited by yopy; 21st November 2021 at 04:26 AM.
-
22nd November 2021, 03:39 AM #26
can't cope with my 520
I am not able to pass the 2nd point
is the MSTMS team working on programmatic patching nav 5
without the need to reassemble the devices?
-
22nd November 2021, 03:43 AM #27
the disassembly itself may damage the device
I destroyed one display in another I damaged the power plug
and I don't think I will make another attempt
nav 5 is problematic to patch, is that the only way?
-
22nd November 2021, 03:54 AM #28
my software version is 21.100.0001.411
the MSTMS patch works in this case
I appreciate your work, but is it the only solution
-
22nd November 2021, 04:21 AM #29
Hi, I did not have time to do it again. All to stay as in the picture since Saturday.
-
22nd November 2021, 04:36 AM #30
the question of how many have been able to properly patch nav 5 with this method without damaging the devices
Blowfish/Meta codes for v1135...
NAV 3 Sayville AE 7F B9 86 F7 16 5C 67 5E 63...