- Go to http://www.ptvupgrade.com/installation/instructions and find
the installation instructions for your box. This will tell you how to
remove the old hard drive and insert the new one.
- Go to http://www.ptvupgrade.com/support/bigdisk/ and download the
LBA48 iso CD (I'm using 3.0) and burn it. ptvlba48-3.0.iso
- On the "PC" connect the old Tivo Drive and the new Tivo Drive to two
different IDE cables. Hopefully, they are all set to "cable sense" on
their jumper settings (the top of the drive will explain this). Most
modern computers have "grey" plugs on their cables for the slave drive
and "black" plugs on their cables for the master drive. They
cannot be on the same cable. Make sure the CD-ROM remains connected
The way I will refer to the drives is this:
| Drive Letter | IDE Location | Description |
| a |
IDE Bus 0 Master |
Where your old hard drive was connected and where
the old TiVo drive probably is now |
| b | IDE Bus 0 Slave | probably empty |
| c | IDE Bus 1 Master | probably your CD-ROM drive |
| d | IDE Bus 1 Slave | probably your new TiVo Drive |
So, in my box I have a=OldTivo, c=CDROM, d=NewTivo.
NOTE: MAKE SURE NO WINDOWS 2000/XP DRIVES ARE ATTACHED TO YOUR
MACHINE. God help you if you do.
- Book up the box and put in the burned LBA48 CD in the drive and boot
from it. You'll get an error if it's not in, just put it in and
restart.
Backup The drive
- Just to make sure you did it right, type in the following:
mfstool info /dev/hd?
Where `?' is the letter of the drive you think it is. It should
give you valid information about your drive.
Then, Type in the following command replacing the ?'s
mfstool backup -Tao - /dev/hd? | mfstool restore -s 127 -pxi - /dev/hd?
Where the first `?' is the same as above and the second `?' is the new tivo
drive.
Note: Please, please, please do this right. The old one first, the
new one second. Otherwise you're screwed and need to spend $20 on a
InstantCake cd from ptvupgrade.com
for example, I have hda as the old tivo drive and hdd as the new drive
mfstool backup -Tao - /dev/hda | mfstool restore -s 127 -pxi - /dev/hdd
This will take a long time. I'm going on a hike in the meantime. If
you don't want to backup all your old programs, google "mfstool backup"
to find out which option is right for you.
Note: if it seems to "hang" around 100-150, reboot and try again. I
found that about 50% of the time it would have this "hang". So don't
skip out until it hits 200 or so.
- Type in "halt". Turn off the machine, disconnect the power, and
remove the old TiVo drive. Put it into storage. Get it out of the room!
Then reboot the machine.
Mod the kernel and enable telnet
The default kernel that comes on the Tivo won't let you hack
anything. You need to mod it with the "killhdinitrc" script. But,
since you've downloaded the CD, the kernels are already on the drive.
For the next parts, replace hd? with the location of the drive
above
- Mount the "var" partition
mount /dev/hd?9 mnt
If this doesn't work, you're on your own. The hd?9 partition is the
/var directory of the running tivo box. The hd?4 partition is the
root partition (which is read-only)
- Unzip the hacked kernel
Now we're going to make a directory to hold the new & old kernels.
cd /mnt
mkdir hack
cd hack
mkdir kernels
cd kernels
cp /cdrom/s2_kernels/4.0.1a/vmlinux.px.gz .
gunzip vmlinux.px.gx
mv vmlinux.px newkernel.px
If you have a different software version, pick an different kernel.
- Use tpip to update the kernel
tpip -k newkernel.px -o oldkernel.px.bak /dev/hd?
This will create the "hacked" kernel that will avoid the "initrc"
checks.
- Create the rc.sysinit.author file to start a telnet daemon.
We're now going to create an /etc/rc.d/rc.sysinit.author file. This
file is called near the end of startup to allow TiVo to debug the
system. We're going to add our modifications to this file
# Mount the root partition
cd
umount /mnt
mount /dev/hd?4 /mnt
cd /mnt/etc/rc.d
vi rc.sysinit.author
Then add this to the file:
#!/bin/bash
PATH=/bin:/sbin:/var/hack:/tivobin:/tvbin
TIVO_ROOT=
MFS_DEVICE=/dev/hda10
IGNOREEOF=1000
export PATH TIVO_ROOT MFS_DEVICE IGNOREEOF
echo Turning off firewall ... >& /dev/console
[ -x /etc/netfilter-disable ] && /etc/netfilter-disable
echo Enabling telnet daemon ... >& /dev/console
tnlited 23 /bin/bash -login >& /dev/console &
- Line 2 sets the path correctly for future hacks
- Line 3-5 are needed for mfs_ftp (And it's hda10, regardless)
- Line 7 disables the firewall if it is enabled
- Line 9 starts the telnet daemon.
Then, you need to make it executable
chmod 755 rc.sysinit.author
- Type in sync then halt and then power off the machine.
Remove the drive from the machine.
Start up the Tivo box
- Place the new drive inside the Tivo box according to the
instructions. Make sure you have all the cables attached, especially
the one that goes to the front of the . Make sure you have screwed the
hard drive down. Make sure you have the case closed (you don't need to
screw it tight)
Then power it up! It should "work correctly".
Connect to the TiVo and remove encryptions
- From a computer, telnet to your Tivo. You should get a bash
prompt. Success! It's now hacked. If not, you can reconnect it to the
PC, mount hd?9, and look at the /mnt/log/kernel
log. It should explain the error.
- Hack the tivoapp to remove decryption.
The original information is here:
http://www.dealdatabase.com/forum/showpost.php?p=139455&postcount=1
The echo line is what is different in each version. You must type it
in exactly.
mount -o remount,rw /
cd /tvbin
cp tivoapp tivoapp.orig
mv tivoapp tivoapp.tmp
cp tivoapp.tmp tivoapp
chmod 755 tivoapp
echo -ne "\x3c\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=8618248
mount -o remount,ro /
At this point, you could reboot or keep going. In any case, you'll need
to reboot either with the 'reboot' command, or to restart tivo itself.
You must do this while the tivo itself is running. Don't try to do it
from linux or you'll hose your box. If it works, you can delete tivoapp.tmp
- Copy & start tivoftpd
You can follow the instructions here...
http://www.tivohelp.com/archive/tivohelp.swiki.net/50.html
Or you can download it directly
cd /var/hack
http_get -T 0 -C 0 -D /var/tmp -U http://homepage.mac.com:80/steventamm/software/tivo/tivoftpd
chmod 755 tivoftpd.
I put homepage.mac.com in italics because you may need to use the
ip address.
Then start tivoftpd.
./tivoftpd.
- At this point, we're ready to copy over anything. We need the
following:
- vserver: This will allow streaming of unencrypted Tivo
files accross the internet. You can find it using http_get from
the same place replacing tivoftpd with vserver. Otherwise, google
vserver.mips or vserver.mips.zip
- mfs_ftp: This is useful for making archival backups (.tmf files)
http://dealdatabase.com/forum/showthread.php?t=21915
I've gone through the trouble of creating a 1.2.9p S2 version that
you can just use.
http://homepage.mac.com/steventamm/software/tivo/mfs_ftp129p.tar
tar it into /var, it will create everything you need. Read the
readme to figure it out. BTW, it hates passive ftp.
- tivotools: A busybox installation, so you get things like
"ls". Unpack it into /var/hack.
http://homepage.mac.com/steventamm/software/tivo/tivotools.tar
- tivowebplus: Get it from here. http://tivo.fp2000.org/twp/. I'm not a
big fan of it's installer, it adds stuff everywhere. Follow manual
installation, and make sure you modify tivoweb.cfg to make sure
TyShowLinks = 1.
You can ftp them, or copy them.
You can start them as well..
- Modify the rc.sysinit.author file to startup these things next time
you reboot
mount -o remount,rw /
vi /etc/rc.d/rc.sysinit.author
... Add the following lines
echo Starting FTPd ... >& /dev/console
tivoftpd &
echo Starting vserver ... >& /dev/console
vserver &
echo Starting mfs_ftp ... >& /dev/console
/var/mfs_ftp/mfs_ftp.tcl
echo Starting tivowebplus ... >& /dev/console
/var/hack/tivoweb-tcl/tivoweb &
...
mount -o remount,ro /
- Optional: Run the ciphercheck.tcl script to make sure you are
recording unencrypted.
- Get mplayer for your particular computer, connect to your tivo as
outlined here:http://tivo-mplayer.sourceforge.net/
Then just search the internet for things that involve "ty" files, and
there you go.