Activity Stream
154,435 MEMBERS
1167 ONLINE
GPSurl On YouTube Subscribe to our Newsletter GPSurl On Twitter GPSurl On Facebook GPSurl On Google+

Page 38 of 61 FirstFirst ... 28363738394048 ... LastLast
Results 371 to 380 of 608
  1.    Cracking <2010 devices that connect through MyDrive rather than TTHome   Cracking <2010 devices that connect through MyDrive rather than TTHome Cracking <2010 devices that connect through MyDrive rather than TTHome
    #371

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    hey i did some stuff.. port scanning and device scanning and tt recovery mode and now i see it as an network connection, and it has an extra open port 3129, i'm going to try to change the ip adress, it has file and folder sharing on too but i cant browse the device yet, i'll keep you updated

    [Login or Register to remove this advertisement]

  2.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #372

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.


    I inserted my own key for the root user below the regular key in the /root/.ssh/authorized_keys file, so both keys should have worked. It doesn't matter what happens with MyTomTom as long as I get a network connection to it and it doesn't overwrite my settings.

  3.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #373

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    Right, which is why I tried to enable an extra key for the root user. It's a custom busybox build, so they just didn't enable that many services. I intend to get ssh access to my TT. I haven't had time to mess with this in a few days, but I might try again tomorrow.

  4.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #374

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    Looking into it, the SSH daemon is dropbear which is a busybox option. I am going to investigate how this is set up.

    Code:
    Only the registered members can see the CODE Contents. Please Login OR Register.

  5.   Advertisements

  6.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #375
    TomTom Master
    rusigor's Avatar


    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    Guys, you just wasting your time. As long as U-boot controlling in-out traffic, nothing you can do with software tools.

    I've bought START-20 device just for experiments. The aim is - to get dump from internal flash including U-boot sector. Just waiting instructions of you how to do this (obviously it can't be done without soldering kit etc, but I'm ready to do this).

    PM preferred.

    Cheers

  7.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #376

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.

    I gave you everything that you need to do this short of the part number on ebay, but I didn't post a link because I'm pretty sure that that's against forum rules. Once you have connected the SD card reader to the TT, that is basically IT. If you look in the video, you can see where the very first thing that I am doing is creating a 4GB image of the device including the U-Boot area. There is no uboot.conf in any of the three mountable partitions. This is in agreement with the console dump that I posted on the OpenTom wiki several months ago.

    Link URL:
    Only the registered members can see the Link URLs. Please Login OR Register.


    I have some more to read before I definitively say anything about the bootloader and its locations, but it appears to be that there is a chain that does something like this:
    reset vector code -> U-Boot -> Linux

    What complicates this is that there is a BootIt partition. There might be an actual BootIt Bare Metal installation on there, or maybe they just liked the sound of the name. Whatever the case, partition 9 has the actual boot flag and is what U-Boot loads.

  8. The Following 2 Users Say Thank You to parasonic For This Useful Post:
    [ Click To Expand ]

    daniele57 (17th December 2012),simba (17th December 2012)

  9.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #377

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    Quote:
    Only the registered members can see the QUOTE Contents. Please Login OR Register.


    So what this means is that a SSH server daemon is started which disallows passwordless logins (-s), dumps the errors to stderr, and isn't (this I don't understand the reason for) sent into the background. Both of the commands use a key at /etc/pnd.dss, so this might be why I was unable to log in using keys in the user directory. I will have to read about dropbear to find whether this is actually the case.

    I'm going through the files which I dumped. I had to desolder everything in order to get the TT to boot. Even clipping the wires down to about 1 cm caused the unit to not power on.

  10.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #378

    re: All <2010 devices that use connect through MyDrive rather than TTHome

    parasonic
    you say, that creates an image of 4 GB of the device including the U-Boot area.
    wonder, the tomtom for these tests using its internal memory is 4GB? can confirm that?
    this says that 4GB is a file.img
    greetings.

  11.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #379

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    Yes, my TT has a 4GB flash device.

    In order to mount the image, you can use kpartx as follows:

    Code:
    Only the registered members can see the CODE Contents. Please Login OR Register.


    And to add what the table looks like (as seen in the video):

    Code:
    Only the registered members can see the CODE Contents. Please Login OR Register.

  12. The Following 1 Users Say Thank You to parasonic For This Useful Post:
    [ Click To Expand ]

    simba (17th December 2012)

  13.    Cracking &lt;2010 devices that connect through MyDrive rather than TTHome   Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome
    #380

    Default re: All <2010 devices that use connect through MyDrive rather than TTHome

    i dont know it you can do anything with this but here is a support website where you can download a lot of linux networking tools for tomtom including busybox, maybe there are some certs in the tars

    tomtom.com/page.php?Page=GPL11x

Page 38 of 61 FirstFirst ... 28363738394048 ... LastLast

Similar Threads

  1. [HELP] Help with TT GO 6000 and connecting to MyDrive
    By thirkell in forum TomTom Discussions
    Replies: 1
    Last Post: 13th February 2016, 02:53 PM
  2. Replies: 1
    Last Post: 4th February 2015, 10:20 PM
  3. NAV3 devices that use v10-v14 navcore and MyTomTom/MyDrive connection
    By biggerdave in forum TomTom Models Listing
    Replies: 0
    Last Post: 8th May 2012, 03:32 PM
  4. Garmin CHINA City Navigator NT 2010.32
    By HULK in forum Garmin Maps
    Replies: 0
    Last Post: 5th March 2011, 01:32 AM
  5. City Navigator Singapore/Malaysia NT 2010.40
    By HULK in forum Garmin Maps
    Replies: 0
    Last Post: 5th March 2011, 01:22 AM

Tags for this Thread

Amount:

Enter a message for the receiver:
BE SOCIAL
Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome Cracking &lt;2010 devices that connect through MyDrive rather than TTHome GPSurl On Facebook Cracking &lt;2010 devices that connect through MyDrive rather than TTHome