Page 1 of 20 12311 ... LastLast
Results 1 to 15 of 353

Thread: Overview of Hacking an S3

Hybrid View

  1. #1
    Join Date
    Feb 2007
    Posts
    24

    Overview of Hacking an S3

    If you've got an S3 you want to hack I've written this overview to point you in the right direction. Telnet bash and ftp are the foundational hacks. With them the door is open to any other modification. This is not a guide, but an overview. In very broad strokes, the steps you'll need to take to get the foundational hacks working. These will also apply to the late model S2.5 versions.

    Getting a Bash prompt and ftp on my S3 took 3 days of reading and reading ... and reading. I've owned and modified an S1, and an early S2 so I was surprised at how research was required to find the answers I needed.

    In the course of reading dozens of posts I got the sense that some folks here are "anti-guide" they prefer newbies use the same approach as me. These are people who have been reading these posts for years. Perhaps they don't realize that within a 415 post long thread there are maybe 6 important posts. I concluded that what DDB needs is not a set of guides but a useful index. An index tells where to find the most relevant threads or posts to address specific topics. The search function is useful but the key to an index is relevancy. Searching for "initrd" will return thousands of posts, but won't tell you which ones define what it is and why it is important to the tivo hacker. A well designed index to quality posts could enhance DDB a great deal. Currently there is no good way to do this.

    Please think of what follows as a type of index to the essential information for the initial cracking of an S3. This is really for my own use so that in 2 years I won't have to start from scratch if I need to retrace my steps. After developing it, I decided to share it here.

    Of course it goes without saying that modifying your tivo in any way is a breach of the user agreement. There is no way to hide these changes from Tivo, INC. Since the tivo needs to call in every day they could test any of a dozen indicators as part of the daily call to check for hacking.

    1. The Tivo has a number of features specifically designed to keep you out of it. These build on top of each other like a stack of books. Read the write up S2 chain of trust.

    2. Currently the S3 can only be cracked by replacing the software in an EPROM chip soldered to the motherboard. Read the thread on the S3 prom hack for details.

    3. Get the EPROM in your S3 socketed. A socket allows it to be pulled at will for re-programming. This is no more difficult than indoor wall climbing, but it does take skill and some special tools. There is no thread which explicitly spells out how to do this, but there are good tips in the S2 support forum under PROM socketing

    4. Get the EPROM (once removed) reprogrammed. This takes some special equipment.

    5. Modify the kernel (this should be obvious from the Chain-of-trust thread), specifically a portion known as initrd. This is a tricky topic to research since there are so many threads, but most assume the reader already knows the basics. Look in the S2 forum for the tiny initrd thread. Read every post. I also discuss this below in post #9 of this thread

    6. To modify the kernel, you need to get the tivo drive in a PC computer running Linux. You'll need a SATA port on your desktop PC and a specialized linux boot disk. As of March 2007, I'm finding the best ISO for this purpose is at mfslive.org However Mr Black's replace_initrd is not compatible with the version of DD on the mfslive boot disk. I haven't looked into why this is yet. You will need another linux environment to actually edit the kernel in.

    7. Copy tivoftpd to the Tivo drive while the tivo drive is in the PC.
    8. Copy Alpha Wolf's All-in-one utilities to the TiVo drive while the drive is in the PC.

    9. With the tivo drive in the PC, create an rc.sysinit.author file to:


    10. Once it's running probably the first thing you'll want to do is get a copy of ls on the machine. This is easily done by ftp'ing in alphawolfs all-in-one tools.
    Last edited by buechel; 02-16-2008 at 04:22 PM.

  2. #2
    Join Date
    Feb 2007
    Posts
    24

    So what is a prom socket anyway?

    Socketing a PROM is so precise and exactly the same for every S3 owner that I feel comfortable writing a guide for this process. This is forum for hobbyists, yet it is somewhat rare for computer hacking skills and electronic soldering skills to coexist in the same hobbyist.

    To socket an S3 I use the following tools and supplies

    - 30W / 15W switchable radio shack soldering iron with a sharp and well tinned tip
    - Fine electronic solder
    - About 10 cm of ChipQuick alloy
    - Radio Shack desoldering braid
    - ChipQuick flux
    - 3M surface mount PLCC32 socket 3M part number 8432-21B1-RK-TP Get it at mouser.com
    - Utility knife
    - Small needle nose pliers
    - A dozen Q-tips
    - Isopropyl alcohol
    - Magnifying glass
    - Ohm meter to check for shorts and mis-soldered pins

    The best DDB threads for general tips are
    This one in the Buy/Sell forum
    This one in the S2 Support forum

    Both threads include many approaches and methods. Here is my method:

    After removing the hard drive and getting the box on a bench with bright lighting,

    1. Prepare the TIVO.

    Get the box on a bench with good light and ventilation.
    Remove the hard drive.
    Remove the clock battery.
    Take static electric precautions. Either use a ground strap (I connect it to my ankle to keep my hands free) or get the room humidity over 50%.
    Tape off the area around the prom to prevent possible splatter contamination / shorting of nearby parts

    2. Follow the ChipQuick instructions to remove the PROM

    - Apply a bunch of flux to all pins
    - Melt a bunch of the alloy to bridge the 8 pins on each side.
    - Rapidly heat different sides with iron until the chip slides around
    - Lift the chip off with a pair of small pliers
    - If you lift a pad, this is not the end of the world, extremely delicate surgery might be able to save the device, by transplanting a few stands of copper from a de-soldering braid onto the trace to form a new pad. Best not let this happen though

    3. Clean the Pads

    While melting the remaining alloy, use Q-tips to push the alloy / solder mixture off the pads. After the blobs harden remove them with fingers or tweezers.
    Using plenty of desoldering braid laid flat across a row of pads heat the solder and pad through the braid. Do not linger in any one place long. Be sure to run a fine balance between getting the pads clean enough that good joint is possible and between overheating the pads detaching them by melting the underlying PCD
    Clean the pads and area with Q-tips and alcohol. Special lint-free versions of the classic q-tip may be desirable since leave less mess.

    4. Clean the Old Prom

    The ChipQuick designers assume the old component will be trashed and the old prom is left with all the pins bridged. To remove the alloy:
    Set the iron to 15W
    Grasp the PROM between thumb and forefinger so that one row of pins is in the clear.
    Heat that row of pins all at once with the side of iron tip until the alloy melts
    Quickly hit your wrist / edge of your palm against a table top
    DO NOT HIT THE PROM AGAINST THE TABLE. Hold on the prom the entire time.
    The liquid alloy should fly off the pins and splatter on the table. Put down some cardboard to catch the mess.
    Rotate and repeat until all pins are isolated. If a second round is needed a little flux can help the process

    5. Prepare the Pads.

    Apply a load of flux the pad area.
    Carefully place a very small amount of solder on each pad. To do this ...
    Touch the iron to the solder to melt a droplet on the tip of the iron
    Touch the iron to the pad to transfer the solder to the pad
    Repeat until all pads have a small bubble of solder on them

    6. Prepare the socket.

    Using a sharp knife cut the bottom out of the socket.
    Cut the plastic lines as close to the connectors as possible
    Do not lose the bottom piece, it will be needed later!
    Use the tip of the knife to pop out the remaining plastic between the connectors.
    Cutting the bottom of socket does not significantly weaken it, once soldered it is very strong. Having the bottom out makes the job of soldering much easier and allows for easier testing of the circuit if there is a problem later

    7. Solder the socket

    Align the socket carefully on the board
    Triple check the socket is aligned properly
    Press the socket down until the 'feet' are resting on the pcd, the pins are springy and will bend up away from the solder pads you laid down.
    When you are sure the socket is perfectly aligned touch the iron tip to one pin. The pin will melt the solder under it and push down to the pad. Once you remove the iron the solder will cool and lock that pin in place.
    Repeat with a pin on the opposite side to ensure good alignement
    Solder two pin on each side
    Finish soldering all pins
    Triple check every solder connection with a magnifying glass
    If there a solder bridge remove it with some braid and re-apply a bit of solder to each joint

    8. Clean up

    Clean the area with Q-tips and alcohol
    Strictly speaking the ChipQuick flux is safe to leave behind, but I don't like the way it looks. Without washing the board, it can't be completely removed though.
    Place the socket bottom you previously cut out in side the socket. Just let it sit there, don't glue it or anything. This will serve to prevent the PROM from bottoming out, which can cause twisting and connection problems

    9. Insert the PROM and cross your fingers.

    Push the PROM down until it bottoms out. With the box still open on the bench plug in the power supply. If the fan starts spinning within 10 seconds you are almost certainly OK. If not, get out volt meter and start checking for shorts or missed connections.

    10. Reinstall the drive & battery, close it up and connect to a TV. See if it boots.


    In the photos below (as attachments) the first is a socket with new PROM in a S3. Notice how close the socket must come to a nearby capacitor.

    The second is a detail in the same S3 of the pin soldering. Notice a little flux I couldn't quite clean in the corners and between some pins. Since the spacing on the pins is about the same as the thickness of mechanical pencil lead, getting the exact amount of solder on the pads is crucial. Too much solder and a bridge is almost inevitable.

    Still too scared to DIY? There may be people offering to do this service for you:
    Attached Images Attached Images
    Last edited by buechel; 12-05-2011 at 01:16 AM.

  3. #3
    Join Date
    Feb 2007
    Posts
    72
    thank you so much for this walkthrough and summary.

    My question:

    what does this get me ?

    I don't know about all the million things people do with their hacked tivos - the ONLY thing I care about is getting full-resolution copies of my TV shows off of the tivo, and onto my unix fileserver so that 20 years from now when I don't have a tivo anymore I can still use them.

    That's it. How close are we to that ?

  4. #4
    Join Date
    Jan 2005
    Location
    Narnia
    Posts
    1,266
    Quote Originally Posted by tiver View Post
    My question:

    what does this get me ?
    It gets you a hacked unit. It gets you a Series-3 Tivo unit which you can telnet into, which you can add/change the (GPL'ed) software on the box, and access to the proprietary files which run the Tivo interface in the event any useful patches are ever found.

    Your other question isn't really a hacking question, so much as an extraction question. Maybe it should go in a new thread. Right now it is still early in the S3's life, so there isn't a lot to say at this point. The TY format on the S3 seems to have been subtly changed so the tools we're all used to using don't work.

  5. #5
    Join Date
    Feb 2007
    Posts
    1
    I would love to do this hack on my Tivo so that I can get some more features on the S3...Caller ID .

    But I dont have the skills to take the PROM off or back on for that matter. Anybody in Greenville SC with skills that can do it for me? For $$$ of course!

  6. #6
    Join Date
    Feb 2007
    Posts
    24

    You want to do what to my PROM?

    The whole point of my earlier post was to socket the prom. Why socket the prom? So we can change it of course!

    Because of the vast number of ways to accomplish the goal of re-writing the prom it is impossible to write a step by step guide. This overview is intended to tell in a different way what has been written many times before at DDB.

    PROM is an acronym for Programmable Read Only Memory. The key nature of this the programmability part. We will change instructions inside the PROM to bend the function of the Tivo more to our liking. By modifying the prom we move down one step in the overview. After this step is complete, the next will be modifying the kernel. You will only need to reprogram the prom once. Once it is fixed you will likely never ever need to change it again.

    When the Tivo first turns on the CPU is hard coded to look for its first instructions at a specific memory location inside the PROM. These instructions are written in "machine language", a set of about 100 different very specific actions which the CPU knows how to do. (To the human, these appear as bunch of almost random numbers. Special software can turn them into a form more understandable, mnemonics.)

    Those instructions need to get the tivo up and running; basically initialize and check some hardware and then load the kernel. Control is passed to the kernel and the instructions in the PROM are then ignored until the next reboot.

    Part of the security in the Tivo as discussed in the chain of trust post is that the instructions in the PROM scrutinize the kernel to make sure it is Tivo Inc, approved. If not the PROM is supposed to refuse to proceed and just stop.

    The easiest way to bypass this is to change the programming inside the PROM a little. Changing just the smallest byte of a machine language program can have a big impact. In machine language, an if-then command is known as a "conditional jump" For example, "if the kernel is legit then load it or else stop" is essentially written as:
    if the kernel is legit then jump to the routine which loads the kernel
    else keep going to the next instruction
    stop
    .
    .
    .
    Routine which loads and runs the kernel ...

    changing just two bytes turns that into
    jump to the routine which loads the kernel

    stop
    .
    .
    .
    Routine which loads and runs the kernel ...

    The trick is to find where that command is inside the PROM and change it.

    Fortunately others have already done so for virtually every Tivo. The addressing notation is in hex

    For the S3 with prom 3.16, the changes are documented here

    For the 2.5 'Nightlight' TCD540xx with prom 2.25 the changes are here

    For the S2 dual tuner, the changes are here

    By far the hardest part of reprogramming the prom is getting appropriate hardware to do it with. Once you have that in hand it really is a snap. What equipment is needed to reprogram a PROM? There are several options:
    • A specialized tool known as a "EPROM programmer" is the easiest choice since it usually comes with software to perform the needed functions.
    • other cheaper options, including using a socketed early S2, using homieflash
    • or a various PC hard drive controller cards. These are little more difficult since they do not automatically have user friendly software.


    Broadly speaking there are several discrete steps involved in reprogramming the prom:

    • use the Eprom programmer software copy the contents of the original prom to the PC
    • save a copy to the hard drive of the PC as a file
    • edit the right bytes in the code.
      Cut out the compressed section with some hex editing software. I like 010 editor but only because it was the first one I found. I'm sure there must be very functional free options out there.
      in cgywin or some other linux environment use gzip to expand the compressed section
      use hex editing software to change the right bytes
      use gzip to compress the modified section
      use a hex editor to paste the modified section back in
      save the result as file
    • get a new prom chip in the programmer
    • write the modified code to the new prom


    For the S3 and the DT versions a linux environment is needed to use gzip uncompress and parts of the code before editing. A good choice for my needs on a windows PC is cygwin.

    As of March 2007 an EPROM programmer will run about $60 on eBay.

    Because there are so many ways to accomplish this task, I won't create a blow by blow walk through. If you are doing this yourself, you need to adapt the previous steps to your situation.
    Last edited by buechel; 03-25-2007 at 09:19 PM.

  7. #7
    Join Date
    Feb 2007
    Posts
    72
    ok let me ask a different question (or perhaps the same question, a different way).

    Now that you can hack the PROM, etc., do you have all the tools you need to work on video extraction ?

    I understand the format is different and things are done differently than on S1/S2 ... I realize there is still (soft) work to be done. But does the PROM hack mean that all the heavy lifting is done and that all of the tools are in place to get extraction going ?

    Is it now just a question bits and bytes ? Or are there additional hard(ware) problems to solve ?

    I wonder if tivo, deep down, knows that there are a lot of people out there (myself) that would immediately pay any price for an S3 if video could be extracted from it...

  8. #8
    Join Date
    Jan 2005
    Location
    Narnia
    Posts
    1,266
    Quote Originally Posted by tiver View Post
    But does the PROM hack mean that all the heavy lifting is done and that all of the tools are in place to get extraction going ?
    Hacking the PROM really just refers to removing the SHA1 signature check done on the Tivo's kernel. At this point you can run a modified kernel. Specifically: A kernel which doesn't fall into an initrd filesystem check as it boots.

    In the sense that a PROM-hacked S3 gives you access to your own machine, then yes the 'heavy lifting' is done once you socket the PROM and fix the PROM code running on the chip. Everything else is pretty much a matter of figuring out software bits and bytes, as you say.

    There is still a lot to be done with figuring out encryption on the recordings, and the 'new' format of the TY files. The S3 is still very much a minority unit, plus a lot of the heavy duty figure-it-outers on this site seem to be satellite users, so it might be a long while before a lot of useful tools ever get built. You need to decide if the S3 does what you need now, and can live without file extraction, before you drop money on it.

  9. #9
    Join Date
    Feb 2007
    Posts
    24
    Quote Originally Posted by tiver View Post
    Now that you can hack the PROM, etc., do you have all the tools you need to work on video extraction ?
    Hacking the PROM is to video extraction as running the first mile is to finishing a marathon.

    In terms of difficultly there are two different aspects:

    1. To design the hardware modification described at DDB is not that difficult. To implement them is difficult due to the touchy soldering and and need for special equipment.

    2. To design the software modification is extremely difficult but once they are created and released, implementation should be relatively easy (assuming you have already implemented the necessary hardware modifications)

    There are also various reasons for prom socketing which have nothing to do with video extraction, such as the caller ID program and the fan speed modification

    The intention of this thread is paint broad strokes of how to get an S3 to the point that when any software mods are built and released they can be installed. I will never in this thread discuss video extraction or any other software modification beyond getting telnet and ftp running.
    Last edited by buechel; 03-11-2007 at 10:42 AM.

  10. #10
    Join Date
    Feb 2007
    Posts
    24

    Pop that Kernel

    Modifying the kernel on your shiny, prom modified S3

    The TiVo is a Linux machine. At the heart of Linux is the kernel, a program that oversees the operation of a computer in ways similar to traffic lights. Generally the kernel has no "will" of its own. It exists only to allow other computer programs to function. There is though the possibility of an "initrd", a space where programs can be stored and run before anything else.

    In the case of the TiVo S2 and S3, the initrd will contain a program that checks the file system of the TiVo for unauthorized modification and if it does find them, it attempts to destroy them. If it fails the TiVo won't boot.

    The solution is to replace the contents of initrd with something more benign.

    Enter stage right: alldeadhomiez's tiny initrd. This initrd replacement was created in Feb 2003 for the S2, but still works great on the S3 since the hardware is still in the same 'family'. The program in the replacement initrd does nothing at all, except to return an "all clear" signal to the kernel so that booting can continue normally.

    The purpose of this post is to demystify how to replace the original TiVo initrd in your S3 with the benign version.

    Shortly after alldeadhomiez created the initrd replacement, Mr Black in March 2003, created a C program to scan a kernel, find the initrd segment and automatically patch in the tiny initrd replacement. Thanks to NillaZilla a complied version of this program can be found at this thread.

    Edit: The discussion in the next two paragraphs is no longer an issue. NillaZilla's complied version now includes a busybox compatible version of replace initrd.

    Unfortunately there is a problem with Mr. Black's program. It relies on a linux tool, DD. DD is a program for copying sections of data to and from a hard disk. DD is implemented differently in various distributions of linux. Various linux bootdisks, such as the version as mfslive.org use busybox to implement DD. Mr. Black's tool won't work with that linux distribution since the workings of DD are subtly changed. I know that the PTV upgrade linux disk will work, but that the mfslive.org version will not.

    I say all that because there is yet another complication - SATA. Most TiVo aware linux distributions do not play well with SATA. The PTV upgrade version does not work with many SATA inferfaces, but the mfslive.org version does very well. This creates something of a Gordian Knot. I can read the kernel with one version of linux, but can only edit it with another. Sigh. The result is a long procedure where the kernel must be copied from the tivo disk to a Parallel ATA drive, then reboot into a different linux version, edit it, boot back into the SATA aware version and copy the edited linux onto the TiVo drive.


    Many of the steps of this process are demonstrated in the tiny initrd replacement thread unfortunately the thread reads like a mystery novel. The information is there, but it is not in any good order, nor is it complete as "walk-through" you will need to fill in the gaps. I recommend reading every word of first 35 posts. 5 of those posts are useful, but are only meaningful in context. Read them all again. Build a plan of what steps must be taken and in what order. Get every command you will need to type written down / printed out before you open the case on your TiVo.

    Since that thread describes the actual commands to enter, I won't replicate them here. What I will do is share the outline of my plan.

    0. Collect tools.

    1. Connect the TiVo drive to my PC and boot with mfslive.org disk
    'mount' a FAT32 drive so I can copy files to it
    2. Use bootpage to figure out which the partition the active kernel is in.
    3. Use DD to copy the kernel to a new file on the FAT32 drive. DO NOT RELY ON REPLACE_INITRD TO PROPERLY BACKUP THE KERNEL
    4. Use busybox.replace_initrd to patch the kernel.
    5. Copy tivoftpd, AlphaWolf's Tools to the tivo drive. (Get tivoftpd by expanding AlphaWolf's tools on the Fat32 drive. I find that AlphaWolf's tools need to be installed on a running tivo, so just copy the tar file to the tivo drive and wait until you are logged into the tivo via telnet to expand it.
    6. Create an rc.sysinit.author file on the tivo drive to start telnet and ftp at bootup. Chmod +755 rc.sysinit.author so it can be run.

    Sample rc.sysinit.author file
    Code:
    # Add /tivo-bin to path
    export PATH=$PATH:/tivo-bin
    
    # Start telnet
    tnlited 23 /bin/bash -login &
    
    # Disable firewall
    iptables -F
    
    #start FTP
    /tivo-bin/tivoftpd
    That's it. If everything works out right the boot is successful and I can then telnet in. Because there is no ls yet available, I blindly navigate to /tivo-bin and use cpio to install Alpha Wolfs tools.
    Last edited by buechel; 02-16-2008 at 04:49 PM. Reason: Add clarity and update to reflect new tools

  11. #11
    Join Date
    Aug 2004
    Posts
    4,086

    Custom kernel

    Here's another alternative to using the stock kernel with the initrd replaced: link.

    I get outgoing netperf speeds of about 75mbps with the stock kernel and the builtin ethernet, 90mbps with the custom kernel and still the builtin ethernet, and ~150mbps with the custom kernel and the backport drivers with jumbo frames and a AGIGAUSB gige dongle. Incoming numbers are lower, but show similar improvement.

  12. #12
    Join Date
    Feb 2002
    Posts
    6,414
    There is a simple solution to working with an S3 SATA drive using the popular PTVUpgrade boot CD without requiring SATA support. Get yourself one of these SATA to IDE adapters and your S3 drive will be treated just like any other IDE drive. It's the only SATA to IDE adapter I've found that doesn't plug directly into the IDE connector on the mainboard, thereby limiting you to either a single drive or two SATA drives only. You can use your existing IDE cable and have a 2nd IDE device attached along with the SATA drive and adapter.

    I agree with buechel's assessment that figuring out how to use the replace_initrd script is a bit cryptic but it's not difficult once you learn the ropes. I found out the hard way that the mfslive boot CD doesn't work for this process (thanks to Jamie for helping me with this), hence the SATA to IDE adapter. I performed the replace_initrd function in my PC after copying the kernel to my FAT32 drive. Using NillaZilla's replace_initrd.x86 script and the included null-linuxrc.img.gz file, I used the following command:

    /mnt/dos/replace_initrd.x86 /mnt/dos/vmlinux.px /mnt/dos/null-linuxrc.img.gz /mnt/dos/original_kernel.bak

    where vmlinux.px is the copy of the extracted kernel from the S3 drive and original_kernel.bak is a backup copy of the unpatched kernel (this is created as an output to the above process and is not something you need to create ahead of time). You could probably eliminate the extraneous path information by navigating to the root partition of the mounted FAT32 partition but this worked for me as is. Note that the null-linuxrc.img.gz file is not extracted and must be used in compressed form. Copy the patched kernel back over to the S3 drive using the dd command and you should be good to go. I added Alphawolf's binaries and an rc.sysnit.author file to the active partition while I had the drive in my PC so I would be able to use the network connection right away, assuming everything worked correctly (which, fortunately, it did).
    Last edited by captain_video; 03-29-2007 at 09:27 AM.
    Please don't PM me or any other members looking for personal assistance. You'll do better by posting (after you've exhausted the search feature, of course) and taking advantage of the collective expertise of the membership instead of a single individual that may or may not be able to help you. Thank you and enjoy your stay at DDB!

  13. #13
    Join Date
    Mar 2006
    Location
    Los Angeles, CA
    Posts
    141
    There is no ls that works with series 3? Or just at that time of the install 'ls' was not in the path or not even ftp'ed over yet???

    Quote Originally Posted by buechel View Post
    [CENTER]
    ....
    That's it. If everything works out right the boot is successful and I can then telnet in. Because there is no ls yet available, I blindly navigate to /tivo-bin and use cpio to install Alpha Wolfs tools.
    from http://www.dealdatabase.com/forum/sh...1&postcount=10
    S3 / TCD648250b - Socketed
    Audio out of sync

  14. #14
    Join Date
    Jul 2005
    Posts
    507
    Quote Originally Posted by Offspring2099 View Post
    There is no ls that works with series 3? Or just at that time of the install 'ls' was not in the path or not even ftp'ed over yet??
    You misunderstand. He was saying "since LS isn't on the system yet I had to navigate manually and copy one over"

  15. #15
    Join Date
    Dec 2005
    Posts
    35

    TivoWebPlus 2.0 on S3

    TivoWebPlus 2.0 seems to work well on the S3. However, looks like the Tivo OEM software is already using port 80. To get TWP working, go to the config directory below where you installed TivoWebPlus e.g. .../TivoWebPlus/config and edit the tivoweb.cfg file. Change the value on the “Port” line from 80 to something else, like 8080. Then restart tivoweb. When you open your browser use the 8080 as the new port for the Tivo. e.g. http://myTivoIP:8080
    Last edited by avpman; 04-03-2007 at 06:19 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •