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

Page 39 of 61 FirstFirst ... 29373839404149 ... LastLast
Results 381 to 390 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
    #381

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

    Just another little piece of information. I have resoldered everything and this is a snippet from /proc/mounts of what was automatically mounted:

    [Login or Register to remove this advertisement]

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

  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
    #382

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

    My key was not overwritten when the device was updated, so that solidifies some theory.

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

  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
    #383

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

    Making a couple of changes which should hopefully get me in:
    Code:
    Only the registered members can see the CODE Contents. Please Login OR Register.


    I shall rename the key and replace it with my own. Also, to create some free space on this mount several days ago, I did the following:

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


    This frees up a few hundred kB. You can also remove comments from some of the config files or do something similar so that you can make changes in the FS.

  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
    #384

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

    Going by this,

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


    I also decided to put the -g flag on both lines of the service_sshd.conf file.

  5.    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
    #385

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

    This didn't work, and neither did copying the pnd.rsa off the TT and using that. Going back to my Windows PC, I did the following.

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

    mykey is a generated private key whose public key is in /root/.ssh/authorized_keys and pnd.rsa is in the device's /etc directory. If I had to guess, I would say that this is the same key as the "C:\Program Files (x86)\MyTomTom 3\Resources\TT_root_sign_cert crt.dat" file. I can't compare the two though without a little work as the pnd.rsa is not in the human-readable format. If I wanted to poke around, I would be tempted to start here:

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


    And now I shall resolder everything yet again and replace the pnd.rsa with my own.

  6.   Advertisements

  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
    #386

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

    Again, looks pretty good. Please check your soldering jobs with a magnifier lest you short something!


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

    daniele57 (17th December 2012),Mobile_Guru (18th 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
    #387

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

    From the documentation that I have read, pnd.rsa and pnd.dss shouldn't matter. I think that they are supposed to be used in the cryptography for the "keyless" ssh connections where the server sends the client a key and then asks for a password. That's my guess though I haven't had much time to go through their docs. I am more familiar with OpenSSH. Another problem that I may be experiencing is the permissions on the /root/.ssh/allowed_hosts file. I don't have access to the TT right now, so I will continue to look into this. Short of getting SSH working, I might become very lazy and copy over a little telnet server. This isn't nearly as fun, so I would rather spend several hours hacking on dropbear.

    I also examined some init scripts stored in .conf files last night. It appears that there is some way to trigger a dev console by convincing the TT that the Ethernet connection is gone. I already proved on the 2535 on the OpenTom wiki that you can access a console and watch the bootloader and OS start. If memory serves correctly, the variable in the shell script was something like RTS which would likely be a serial signal. Most serial consoles these days don't use CTS/RTS handshaking, but in some cases such as RS232 BlueTooth transceiver chips, CTS and RTS are still used to go between data mode and command mode. Perhaps RTS is used here for a similar reason and needs to be pulled up or down upon power-on to go into factory mode. Now that I have brought this up, perhaps someone will beat me to it?

    I'll play around some more tonight.

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

    biggerdave (18th December 2012),Mobile_Guru (18th December 2012),Shadoow (18th December 2012),simba (18th December 2012)

  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
    #388

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

    parasonic,
    if two comments can help;
    The new TT when preparing the micro SD occupy full capacity but only 25% occupied tubiera if you try to install something you would say that there's no room if you look at the space occupied properties is all free space, eg 4GB micro SD when it is ready to be used by new TT "has created a closed perimeter" that to change within image file would have to remove door open and close not change modify MD5
    Internal Memory guess is the same system.

    example of micro SD prepared for use by new green TT SD serious red perimeter



    U-boot would have to be command mount / umount, (or similar) when mounted lights off picture when disassembled.
    greetings.

  12.    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
    #389

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

    Simba,

    The system partition (partition 6) is the one that I am trying to change. I do not need any more than probably a few hundred kB for my changes. My guess is that partition 7 is a growth area in case partition 6 would need to be expanded. This is only a guess, but the implication here is that partition 6 originates from an image whose filesystem has been resized to encapsulate all of the files and have no free space. Any MD5 sum should not matter as I am avoiding directly dealing with their encryption schemes and updater.

    There is a different partition (partition 9) which is something like 3.7GB if I am remembering correctly, and it probably holds all of the map data which I am not interested in. This is called the "userfs" partition.

  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
    #390

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

    I am back at the machine with the images and have mounted them so that you can see what the capacities are.

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

Page 39 of 61 FirstFirst ... 29373839404149 ... 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