Activity Stream
150,644 MEMBERS
1109 ONLINE
GPSurl On YouTube Subscribe to our Newsletter GPSurl On Twitter GPSurl On Facebook GPSurl On Google+

Page 40 of 61 FirstFirst ... 30383940414250 ... LastLast
Results 391 to 400 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
    #391

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

    Interesting! The rootfs.img file contains the following files.

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

    [Login or Register to remove this advertisement]


    The /etc/init directory on partition 6, however, has the following files.
    Code:
    Only the registered members can see the CODE Contents. Please Login OR Register.


    Maybe this is the difference between normal and factory mode? Maybe in factory mode it boots off this partition instead of rootfs.img, and I should have been editing rootfs.img all along. rootfs.img is a SquashFS image, and you need the appropriate tools to extract the image and create a new one. I didn't have any problem mounting it as a loopback device, but you can't write to it even with the o=rw flag.

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

    simba (18th December 2012)

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

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

    I tried putting my own copy of rootfs in there, and it seems to not like something that I have done. I went ahead and soldered the serial port connection in to get a console.

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

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

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

    A few more pictures...



    TX and RX are actually reversed. The blue wire is data from the PC to the TT.


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

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

    Dang! Wrong block size!

    TT original squashfs info:
    Code:
    Only the registered members can see the CODE Contents. Please Login OR Register.


    Mine:

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


    I have some things to fix.

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

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

    This command may work a little better.

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

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

    Shadoow (18th December 2012)

  8.    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
    #396

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

    I have thought about last night's issues a little and have come to the conclusion that any filesystem that I have altered cannot be mounted by the kernel (zImage). This is the case with both partitions 6 and 9. The bootloader appears to want to boot off 9, fails, restarts, reverts to 6, fails, and gives up. I am not sure whether this has to do with the kernel itself (checksumming, which is unlikely) or the modified filesystem perhaps being on bad boundaries with respect to the flash. My laptop still has no problem mounting the device though. I am going to go through some sources later tonight when I have time.

    Also, the "Non FS data" partition is actually FDT data. FDT stands for Flattened Device Tree, which is a data structure containing information about the hardware to make available to the OS. It is not ASCII, but when I less'ed it, I saw a bunch of the same system info that you see when you access the TT's web server, e.g. battery type, MAC address, etc.

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

    daniele57 (19th December 2012),fylli (19th December 2012)

  10.   Advertisements

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

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

    parasonic
    you may be interested navcore 10 so?



    greetings.

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

    parasonic (19th 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
    #398

    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 do not need NC10 at the moment, but that doesn't mean that I might not eventually need it. Thanks!

  14.    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
    #399

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

    After scouring several packages off TT's site, I have concluded that my problem is still a filesystem issue. I looked at initramfs, U-Boot, and DTC. The file initramfs\src\init.c says everything that is going on at the moment that initramfs tries to mount the partition. There is no checksumming whatsoever. I think that it just wants a clean filesystem. I probably did something that it didn't like when I changed the files in partition 9. fdisk -l complains about boundaries, so I am wondering whether I grew partition 9 outside of its expected area.

    This is what happened after I ran fsck.e3fs on partition 6. Partition 9 was already clean.
    Code:
    Only the registered members can see the CODE Contents. Please Login OR Register.


    I am a little confused as to why it doesn't even see partition 6 anymore. I shall investigate further.

    Edit: it wasn't seeing partition 6 beforehand. Heh...

  15.    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
    #400

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

    Well, I was running against some corrupted data due to a flux build-up and a solder blob on a spot that I assumed wouldn't matter. initramfs now sees partition 9 again. (I think that it might have switched from 1-bit to 4 or 8-bit mmc/sd after U-Boot passed off the execution. The blob was on one of the MSBs in a remote corner.) I am going to be busy for a week or so but will try to find some time to work on this.

    Also, uboot.conf is helpless. If I added anything to it, it wouldn't get me into a console. The flags which a user can specify in that file are very limited. Check out cmd_bootconf.c from TomTom's GPL page if you want a feel for what's going on.

    Also, in their code, bootdelay=0 instead of bootdelay=-1, so it is conceivable that one could get into the U-Boot menu by hitting ctrl+c a bunch of times. I still think that RTS is going to be held high, but I am too lazy and have had too many beers to solder a 10k pull-up to a few pins around the debug connector lands.

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

    biggerdave (20th December 2012),daniele57 (21st December 2012),dthello (21st December 2012),OneLover (3rd January 2013),simba (21st December 2012),tomtom_lover (21st December 2012)

Page 40 of 61 FirstFirst ... 30383940414250 ... LastLast

Similar Threads

  1. Replies: 1
    Last Post: 27th July 2018, 11:37 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