(DEPRECATED) SLEEPER ISO - Series 2 Scripts for U5, Monte and Prom with many hacks

[Sleeper]

Edit by mrblack51:

As evidenced by many posts in this thread and throughout the forum, the "sleeper iso" is both outdated and buggy. Specifically, the default setup installs outdated (ie: old versions of tivoweb, kmem instead of NoCSO, etc), and/or broken hacks (ie: mfs_ftp in some versions, md5sum, joe), uses a non-standard partition layout, and causes unexpected results due to hacks such as the included SPS30 script (search: ghost). While the basic process works, it is highly recommended that you read one of the many threads on using killhdinitrd, which is a better solution. As such, while this method works (with numerous issues that need to be dealt with for a reliable setup), it is not recommended anymore. There is not a another "one step" disk which replaces this one, but there are many boot disks which can be used to hack the drive using the killhdinitrd method. do a search.

edit2: There have been numerous questions/threads/conspiracy theories regarding the ban of sleeper. The facts are clear, and though not being rehashed here (do a search if you are interested), suffice it to say that sleeper will not be responding to any support questions on this board. the ban is permanent and the decision is final, so there is no need to continually bring it up. thanks

edit3 by adh: Requests for TivoScripts support will not be entertained outside this thread. Best bet: just don't use it at all.

edit4 by adh:
Instructions for removing the broken TivoScripts "monte" setup from your drive and upgrading to killhdinitrd:
Unsleeper a 4.0 unit (http://www.dealdatabase.com/forum/showthread.php?t=39580) - PlainBill's unsleepering process

Starting from scratch with killhdinitrd:
Hacking your Series2 in 2004 (http://www.dealdatabase.com/forum/showthread.php?t=38468) - general Series2.0 SA/DTiVo hacking instructions
4.x on a Uma6/RID DTiVo (http://www.dealdatabase.com/forum/showthread.php?t=39354) - installation instructions



Original post follows:

TERMS OF USE
A.) REDISTRIBUTION PROHIBITED IN ANY FORM
B.) SALE OF ANY DRIVE OR UNIT MODIFIED WITH THIS SOFTWARE PROHIBITED
C.) USE OF THIS SOFTWARE TO OBTAIN THEFT OF SERVICE PROHIBITED
D.) USE OF THIS SOFTWARE TO OBTAIN AND DISTRIBUTE COPYRIGHTED MATERIAL PROHIBITED

By clicking on one of the following links you inherently agree to the TERMS OF USE.

Click here to download the latest release of the tivoscritps ISO from pvrfiles.com (http://www.pvrfiles.com.deprecated)

Click here to download the latest version from an alternate site (http://www.b-lan.com.deprecated/tivo/sleeper/tivoscripts1_02.zip)

Click here to download the latest version from TwinBrothers (ftp://tivo:later@ftp.twinbrothers.com.deprecated/tivoscripts1_02.zip)

Latest release is version 1.02 (tivoscripts1_02.zip)
mfs_ftp has been removed.
There are no other changes between 1.01 and 1.02

mfs_ftp See this thread. Do not use the version installed by tivoscripts 1.01 Get the latest version. Read this thread before posting:

http://www.dealdatabase.com/forum/showthread.php?s=&threadid=29459&perpage=15&pagenumber=1

PLEASE READ THIS THREAD BEFORE USING - ESPECIALLY THE PART ABOUT THE REPORTED PROBLEMS OTHER PEOPLE HAVE HAD

I have created automated scripts that perform the U5, Prom and Monte installations for SERIES 2 ONLY!!!!!!

U5 (userland hack) has been removed.

Prom is ONLY for tivos that have a new prom which requires soldering

The scripts are on a bootable mfstools disk (ISO) that also includes many of the more common hacks.

To use them you download the ISO, burn the disk and boot from it. You must install a FAT32 drive as Primary Master, a bootable CD drive as Primary Slave and the Tivo drive as Secondary Master.

The scripts are designed to teach what is happening. Each command that is executed has a brief explanation of what the command is doing and prints out the command. The user is prompted to press enter to execute each command and is then presented with a success or failure message.

The main menu will automatically appear upon boot. All the scripts perform 4 phases, any of which can be skipped. The phases are Backup, Restore, Surgery & Final Installation. However, you can not Restore unless you Backed up with the scripts first.

IT IS STRONGLY RECOMMENDED THAT YOU BACKUP YOUR ORIGINAL HARD DRIVE AND USE A SECOND DRIVE TO HACK. I WILL NOT BE RESPONSIBLE FOR ANY DAMAGE AS A RESULT OF THESE SCRIPTS OR YOUR OWN NEGLIGENCE.

Suggestions, positive criticism, bugs and ehancement requests are welcome.

CURRENT FEATURES/HACKS
Backup
Restore
Monte - U5 kernel & Minimal fs
Prom - Blow out initrd
Network drivers & Config network
tivoftpd
tnlited
tivoweb
/bin utilities
busybox 1.01
joe editor - not working
kmem
prevent daily call (old fixsub)
sort & sps30 scripts
tytools

Probably more that I forgot

For additional info please reference the WIKI:
http://alt.org/wiki/index.php/TivoScripts


The next couple of post are for me to maintain the FAQ about the scripts.

[Sleeper]

DOES YOUR ISO/SCRIPTS CONTAIN THE XXXX HACK THAT ALLOWS ME TO STEAL DTV SERVICE AND/OR TIVO SERVICE

No! Please don't PM me about this. It is against forum rules and illegal and could jepordize all the hard work that I have done for the benefit of others.

I got this error after running the scripts:
Boot failed reason=60
Ram size = 64
Service number is 1010000C0223B7C.
What is password?

Try running the Monte script, not the Prom script!

How far will the u5 and prom scripts get me in the sense of being protected from software updates?

U5 - No longer supported
Monte - uses the upgradesoftware=false on the bootpage
Prom - uses upgradesoftware=false on the bootpage


Are their any task that have to be done to my tivo before using your scripts? (such as reinstating the original RC.SYS and making sure "updatesoftware=true" is still there?

I do not support or encourage that you hack your original Tivo Drive. Do this at your own risk.

Ideally you should start with a virgin unhacked drive that has the latest software on it. If this is your original Tivo drive, install it as Secondary Master and boot the CD. Run a script, perform backup phase, power off and remove the Original drive and install a new drive in its place Reboot and continue with the Restore, Surgery and Final Phases.

If your virgin unhacked drive is not your original Tivo drive and you do not need to expand it or create swap, then install it as secondary master and boot the CD. Run a script, perform backup phase, reboot, skip restore phase, and continue with the Surgery, and Final Phases.

IF YOU ARE HAVING PROBLEMS, PUT THE DRIVE IN THE TIVO AFTER EACH OF THE 3 PHASES (RESTORE, SURGERY & FINAL) AND TEST IT.

Do I need to allow my never before used HDVR2 to call in before I use this ISO?

You do not have to but it is recommended that you force the daily call and pending restart to upgrade. This way you will have the latest software. All of the scripts prevent the upgrade from happening.


After running the scripts, do I need to reinitialize all my hacks?

Just read the screen as you run the scripts. You will see what hacks are being installed. Afterwards, you can edit the rc.sysinit.author or hackint file and remove anything that you do not want. In the future there may be an option to install each utility/hack. Righ now everything gets installed.


What models do you think this will work with? DirecTivos and Standalones?

The scripts should work on all series 2's. They have been tested on both a prom modded HDVR2 and an unmodded HDVR2. There is an option to copy the ethernet drivers. SA units SHOULD NOT copy the drivers. Also 4.x software must manually patch tivoapp - see posts later in the thread


Do you have a .b image I can install on my new 120 A drive so I don't have to wait for the is happen on its own?

The ISO does not contain any images. It may contain the SA images in the future if they prove to work well on a Direct Tivo. If you want the latest software, force your Tivo to do a daily call.


I have the Model XXXX network adapter, does your script support the driver for this device?

The scripts currently installs the pegasus and ax8817x drivers. Others will be added upon request. Please check the other HOWTO threads to see exactly which devices are supported by each driver.


Does the Fix sub included with this ISO automaticly run using cron once a month to keep my Tivo unit activated?

No. It uses the sleep command and runs once per day. I have worked on using crond which is part of the busybox 1.0 toolkit that I installed. The problem is that it wants to use a spool directory under /var and I am still on the fence about that because /var can (although doesn't happen often) get rebuilt and goodbye cron. Opinions on this are welcome.


All hacks are automaticly installed with the ISO, does this mean that they will automaticaly start when the Tivo unit is booted the first time or do I need to implemet them after installing the hacks?

Everything is implemented in /etc/rc.d/rc.sysinit.author
Remove hacks by editing it accordingly. The vi (vim) editor is available over the serial port. Use a terminal like hyperterminal. yyserver must manually be started.

[Sleeper]

What is the differnece between the standard romfs & the delayed romfs?

The delayed romfs has a 2 second sleep before kmonte.o is loaded and a 2 second sleep before monte is run. If you have the problem posted in this thread, try the delayed romfs. Please post your results.

Can I apply the hacks for a> Larger drive installation (to replace the existing drive)

Yes, that is the only RECOMMENDED method.


Can I gain shell access/tivoweb/exraction...and still keep my existing recordings

No. Currently, the backup does not backup your recordings. Also, the noscramble hack is installed so if you somehow have them, then remove the noscramble hack in your rc.sysinit.author.

[Sleeper]

KNOWN BUGS/PROBLEMS/STATUS

FIXES
The ax8817x drivers problem causes the Tivo to continually reboot. The problem is fixed in version 1.01

SA networking firewall issue. The netfilters-disable filter is set to run on bootup in version 1.01


BUGS
SA Tivoweb does not work. This is a problem with Tivoweb - not the install scripts. Once someone posts a fix it will be incorporated.

Joe editor does not work because it was built with the resources in the /hack directory. Will replace when I get a new build. Until then vi editor works. Anyone have it?


RECOMMENDATIONS
Make sure that you start with your ORIGINAL hard drive

Make sure that the drive has the LATEST software version and is completely UNHACKED.

Make sure that the unit is subbed and the DVR service is working.

Make sure that your original drive is not a restore of a previous backup. Something is very funny about backing up and restoring a drive that has already been restored with mfsbackup. I can't put my finger on it but I think that the swap gets messed up.

Do not perform the restore to your ORIGINAL hard drive.


Version history

Version 1.0
1) Removed U5 script.
2) Fixed CallFixSub
3) Allow restore to exact same size drive as backup (NOT SUPPORTED)
4) Added 4 phases - Backup, Restore, Surgery & Hacks
Any phase can be performed or skipped provided that a backup was performed.
5) Alldeadhomiez runmonte fix applied and new romfs
6) Option to install the standard romfs or the delayed romfs.
7) Option for SA users to skip copying ethernet drivers.

Version 1.01 is released!
1) Fixed SA networking.
2) Fixed ax8817x driver
3) Fixed kmem for SA units

Thanks to the beta testers!

[Sleeper]

HOW TO REPORT A PROBLEM

Please post problems to this thread. Please answer the following questions when posting. If the questions are not answered your post will be ignored and a request will be made to have it deleted.

1.) What script did you run? Prom or Monte?

2.) If you ran the Prom script, who soldered your prom into your Tivo?

3.) What model is your unit?

4.) How big is the original hard drive?

5.) Is or has your original hard drive been hacked before.

6.) Have you ever performed a mfsrestore to your original hard drive?

7.) What version of software is running on your original hard drive?

8. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?

9.) What size is the drive that your are restoring to?

10.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.

11.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.

12.) Did you spill coffee on your Tivo while you had it open? Just kidding?

13.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?

14.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?

15.) What model USB newtork adapter are you using?

16) Which network drivers did you choose to install?

[Sleeper]

FAQ part 5

[tivomaster]

I have had the oppurtunity to take a look at the pre-release ISO and I have to say this is one GREAT piece of work.

Thanks Sleeper.

[vertex]

badass, all i have to say is BADASS! i spoke with sleeper on the phone today, great guy great intentions and i love what he is doing for the community!

[tommy78]

I tried it 3 times and it always quits back to the main menu with no error or warning when it gets to the part where it replaces initrd on /dev/hdc3, there is a message for a split second but too fast to read it and then it goes back to the main menu. When I try the drive in the Tivo it gets to the almost there message and reboots, forever.

[vertex]

got mine up and running. anyone know if the tivo itself gets married to your card? im trying to swap cards and when i do it says you have inserted the wrong access card.

[vertex]

all i have to say is sleepers program is great for newbies. i ran it and backed up my original 35 hour, put in a 80 gig and i am up and running. the only problem i ran into was the no call scripts. and that was because i never called in on the tivo. the tivo has to make the first phone call in to activate the dvr service. if you cant monte with sleepers iso, then you need to put your beer down and sober up.

[slim69]

Very nice piece of work - many thanks on behalf of everyone.
I'm running the Monte on an HDVR2. I performed the hacks manually, but tried your ISO and it's great. I do believe people should learn how and why monte works, but a script like your's allows them to see the final result. I have no doubt that once people know they can hack their TIVO, and see the functionality firsthand, they will delve deeper into learning how to do further hacking and maintenance on theirs also. We may also gain some good minds into the community which will benefit everyone. People will be less afraid to take the first step and tinker if they know they can always fall back on a system such as the one you have developed. Again, thanks.

[Sleeper]

So far 3 people have reported problems.

I have attempted to contact on person several time without any success so I can't ascertain what the problem is.

The second person is attempting to use his original drive.

The third case is most puzzling.

It involves a Series 2 SA running 4.0.1 software. (Original Tivo drive os 60G) I am confident that the user performed the steps properly. When his system boots it spits out the following on the console:

Scan /mnt/etc/rc.d
Scan /mnt/initrd
Scan /mnt/lib
Scan /mnt/lost+found
Scan /mnt/mnt
Scan /mnt/sbin
Scan /mnt/var
The filesystem seems to be OK
Scanner main is done
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=3
Freeing unused kernel memory: 60k freed
monte: Two-kernel Monte for MIPS (Version 0.1)
monte: MuscleNerd (MIPS version), Erik Arjan Hendriks (x86 version)
Unable to handle kernel paging request at virtual address 24020600, epc == c0000
490, ra == c00008d4
Oops in fault.c:do_page_fault, line 172:
$0 : 00000000 b0019400 00001000 24020600
$4 : 24c69ee4 8153cf10 00000000 00000020
$8 : 00001000 801d32a0 00000000 3c018017
$12: ac26eef8 81513c14 000000ff 8000ffe0
$16: 8000ff30 80010000 0000e000 00190563
$20: 00001000 c000045c fffff000 00000003
$24: 00000000 00000001
$28: 81512000 81513e60 c000045c c00008d4
epc : c0000490
Status: b0019403
Cause : 80000008
Process monte (pid: 13, stackpage=81512000)
Stack: 801d32a0 ffffffea ffffffff 8000f000 ffffffff 80010000 c00008d4 803
00000003 800486a4 801d32a0 8035c000 00000000 801d32c0 ffffffff c000045c
c0000848 c0000010 fffffff2 800fad50 c000045c 00000041 c0000ec4 00000000
00000006 801d6000 00400b1c 80047cd0 100000e8 00000003 00000000 2ab03a40
00401100 7fff7d6c 0040068c 00000006 00400b1c 1000d40c 00000000 1000d28c
7fff7cc0 ...
Trace: c0000490 c00008d4 c0000ec4 8001c68c 8001cc64 2abe332c
Code: 10910005 00608021 8c630008 <5460fffc> 8c640000 00008021 12000007 0000
0000 8e020004
Kernel panic: Die call

Rebooting in 1 seconds..


Here's the funny part. The script does a mfsbackup of his original drive. I downloaded his backup, ran the script with his backup and monted onto a 137.4 GB drive. (He is using a 120G drive). I put the drive into my HDVR2 and yo and behold it booted just fine. I was suprised to see the SA software boot on my HDVR2.

I then had him extract his initrd nulled kernel and I installed it onto my monted drive made from his image. That worked as well.

He also was able to boot his 120G drive after the restore and before it was monted.

Suggestions welcome.

Sleeper

[Sleeper]

The guy that is Monteing his original drive is experiencing the same error. He is a HDVR2 running 3.1.0. Here's his output:

The filesystem seems to be OK
Scanner main is done
VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=3
Freeing unused kernel memory: 60k freed
monte: Two-kernel Monte for MIPS (Version 0.1)
monte: MuscleNerd (MIPS version), Erik Arjan Hendriks (x86 version)
Unable to handle kernel paging request at virtual address 3c048010, epc == c0000
490, ra == c00008d4
Oops in fault.c:do_page_fault, line 172:
$0 : 00000000 b0019400 00001000 3c048010
$4 : 27bdffe8 83dfdf20 00000000 00000020
$8 : 00001000 8014d2a0 00000000 24840054
$12: 8c820004 83e3dc14 000000ff 8000efe0
$16: 8000ef40 8000f000 0000d000 001b5d65
$20: 00001000 c000045c fffff000 00000003
$24: 00000000 83dfdf30
$28: 83e3c000 83e3de60 c000045c c00008d4
epc : c0000490
Status: b0019403
Cause : 80000008
Process monte (pid: 13, stackpage=83e3c000)
Stack: 8014d2a0 ffffffea ffffffff 8000e000 ffffffff 8000f000 c00008d4 8000f000
00000003 800486a4 8014d2a0 8000f000 00000000 8014d2c0 ffffffff c000045c
c0000848 c0000010 fffffff2 800fad50 c000045c 00000041 c0000ec4 00000000
00000006 8014e000 00400b1c 80047cd0 100000e8 00000003 00000000 00000000
00401100 7fff7d6c 0040068c 00000006 00400b1c 1000d40c 00000000 1000d28c
7fff7cc0 ...
Trace: c0000490 c00008d4 c0000ec4 8001c68c 8001cc64 2abe332c
Code: 10910005 00608021 8c630008 <5460fffc> 8c640000 00008021 12000007 0000
0000 8e020004
Kernel panic: Die called

[alldeadhomiez]

Originally posted by Sleeper
Process monte (pid: 13, stackpage=83e3c000)
Stack: 8014d2a0 ffffffea ffffffff 8000e000 ffffffff 8000f000 c00008d4 8000f000
00000003 800486a4 8014d2a0 8000f000 00000000 8014d2c0 ffffffff c000045c
c0000848 c0000010 fffffff2 800fad50 c000045c 00000041 c0000ec4 00000000
00000006 8014e000 00400b1c 80047cd0 100000e8 00000003 00000000 00000000
00401100 7fff7d6c 0040068c 00000006 00400b1c 1000d40c 00000000 1000d28c
7fff7cc0 ...
Trace: c0000490 c00008d4 c0000ec4 8001c68c 8001cc64 2abe332c
Code: 10910005 00608021 8c630008 <5460fffc> 8c640000 00008021 12000007 0000
0000 8e020004
Kernel panic: Die called

I've run into this before. I believe that invoking monte with, say "exec /mnt/bin/monte $ARGS" instead of just "/mnt/bin/monte $ARGS" fixed it for me, and that changing innocuous things in the chainloader script caused it to come and go if I did not use "exec." YMMV.

[mikand]

Do I need to allow my never been used HDVR2 to call in befor I use this ISO?

[vertex]

have it call in and see if it takes an update, force the call several times. then backup and monte!

[Sleeper]

Originally posted by alldeadhomiez
I've run into this before. I believe that invoking monte with, say "exec /mnt/bin/monte $ARGS" instead of just "/mnt/bin/monte $ARGS" fixed it for me, and that changing innocuous things in the chainloader script caused it to come and go if I did not use "exec." YMMV.

I modified the runmonte script to include exec. Unfortunately it did not cure the problem.

I am using alldeadhomiez 31u5 miminal root file system. I had to put insmod and bootpage in it for monte. The fs is still under 4M.

The "exec" runs it in a different process. So I was wondering if it is a timing thing. Perhaps calling monte right after insmod kmonte.o is the problem. Or perhaps the kernel memory that is freed is not really free yet. So I went ahead and modified the runmonte script. I put sleep 2 in front of and after insmod kmonte.o. This required rebuilding the minimal fs with sleep and a few modules. I also built a new monte_romfs. I tested it out and here is the output when monte loads:

VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=3
Freeing unused kernel memory: 60k freed
Entering Monte
Sleeping for 2 seconds
insmod kmonte.o
monte: Two-kernel Monte for MIPS (Version 0.1)
monte: MuscleNerd (MIPS version), Erik Arjan Hendriks (x86 version)
insmod kmonte.o done
sleeping for 2 seconds
Starting monte
monte: loaded kernel image (target load_addr=0x80002000, len=0x1b5d65) at 0x83e8
f000
monte: total pages used: 439 for image, 2 for indirect tables, 1 for reload code
Loading R5432 MMU routines.

I don't know if this will work but it's worth a try. It will at least indicate if the problem is insmoding kmonte.o or monte.

Sleeper

[Sleeper]

The sleep and exec statements that I put in runmonte seemed to have cured the problem for the person that was monte-ing his SA unit.

How do you spell monte-ing? or is it monteing?

The other 2 people having a problem are currently testing the latest ISO.

[mryuk]

I'm the guy with the monte-ing standalone, and it's working great! I just wanted to commend Sleeper. His script is AWESOME, and he put a LOT of effort yesterday and today into figuring out what was going wrong with my box. Thanks so much for all your hard work!

[Sleeper]

I'm looking for someone that has some bandwidth that is interested in hosting the ISO.

Thanks,


Sleeper

[tommy78]

Has anyone with a DSR7000 gotten this to work?

[newbie]

Sleeper--I've already monted my unit so this is a suggestion not a request: Why don't you put a backup of the b version on the CD? Someone could use your CD to prepare a new drive before even opening up the unit.

[Sleeper]

Originally posted by newbie
Sleeper--I've already monted my unit so this is a suggestion not a request: Why don't you put a backup of the b version on the CD? Someone could use your CD to prepare a new drive before even opening up the unit.

Although that would work, there is nothing to be gained by doing it. The scripts walk you through each step as though you were typing them in yourself.

Yes, hacking a Tivo is not easy for everyone and the average person should not have to spend weeks learning unix before they are successful. Especially Monte.

On the other hand, they should have some idea and interest in what's going on. Otherwise they should just pay someone to hack it for them.

The scrips are a compromise between a "quick fix" as you suggested and a "hard time". I also agree with slim69's comments in this thread. Basically, the scripts will help a newbie become more comfortable at hacking his Tivo and will help himto grow.

Thanks for your suggestion.

[Harry Balzich]

WOW!!!

All I can say its that this worked perfectly the first time. It couldn't be easier and I feel that I learned more with it than I would have without it. I found some of the steps that I was missing in my previous attempts and it explained alot more of why we were doing this step.

Now I just need to learn how to use the bash and take full advantage of this. Time to read up!!!

Thank you Sleeper for a great piece of work. All I can say is that if a dealer gets their hands on this it could be scary. You might want to protect your hard work.

Thanks again and I will keep you posted on any new findings.

Anyone who is having trouble getting the HDVR2 up with monte needs to look into this ISO.

Thanks!!!

Harry

[mryuk]

Well, The newest ISO is TIGHT!! It takes about 15 min total to run the scripts. It’s obvious that Sleeper has put so much of his blood into this. The script couldn’t be simpler to use. (It only asks twice for user input, both questions are network related.)And you have the choice of flying through it or reading the explanations for each step (heaven forbid you learn something!!). This is a work of art. Many hackers will praise sleepers name for a long time.

MrYuk
:mad:

[MiamiTV]

Series 2 Scripts for U5, Monte and Prom with many hacks ISO

I have read this post and It looks to me that this is the way I would like to go. Im hoping that I can get a copy of this Zip.

I have spent ( For Real ) 3 days trying to do this my self, and I have gotten everything to work but the USB port. Oh well.

So I'm in your hands, thanks.

R.

[relay]

2 Issues: 1st, bash is only displaying garbage. No usable text. Was working with previously userland hack. I had my mainboard prom hacked recently and needed to rebuild system. This looked like a great way to try it.
2nd, system reboots after "A few more seconds" screen.
I wonder if this is related to the ethernet drivers issue others were having? I need the ax8817x drivers for my Linksys USB 200M
Must I have 3.1b to use this??? I have forced several calls to no avail. I guess my unit is just not ready for updating. There does not appear to be any other way to get the software.


1.) What model is your unit?
HDVR2

2.) How big is the original hard drive?
40GB

3.) Is or has your original hard drive been hacked before.
No

4.) Have you ever performed a mfsrestore to your original hard drive?
No

5.) What version of software is running on your original hard drive?
3.1

6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?
No. Brand new, not setup yet.

7.) What size is the drive that your are restoring to?
WD 120GB

8.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.
No errors

9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.
All garbage. Used 9600,8,N,1 no flow. Tried a few other settings. This worked fine on previous userland bash hack.

10.) Did you spill coffee on your Tivo while you had it open? Just kidding?

11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?
Yes. Worked fine.

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?
Yes. System worked fine but bash only displays garbage on HyperTerminal.

[mikand]

How do you install additional hacks after using this ISO?

[Sleeper]

relay,

Thank you for providing all the pertanent information and not PM'ing me.

2 Issues: 1st, bash is only displaying garbage. No usable text. Was working with previously userland hack. I had my mainboard prom hacked recently and needed to rebuild system. This looked like a great way to try it.

Are you setting your terminal program up for 115,200 baud, No parity, 8 data bits and 1 parity bit - No flow control?

2nd, system reboots after "A few more seconds" screen.
I wonder if this is related to the ethernet drivers issue others were having? I need the ax8817x drivers for my Linksys USB 200M

Try using the pegasus drivers, I'm working on tracking down the problem with the ax8817x driver. This could be your problem. Also try booting after the Surgery phase and without performing the final Phase.

Must I have 3.1b to use this??? I have forced several calls to no avail. I guess my unit is just not ready for updating. There does not appear to be any other way to get the software.

No you don't need 3.1b, but since software upgrades are prevented it is advised. 3.1 has been tested and works as well.

6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?
No. Brand new, not setup yet.

This has not been tested. One of the original 3 people was unsuccessful mont'ing an unsubbed box. Although he was mont'ing his original drive (mot recommended)

9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.

Change setting and repost error message.

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?
Yes. System worked fine but bash only displays garbage on HyperTerminal.

Diagnosis: Problem with ethernet drivers, Serial port not properly configured on terminal.

Temporary fix: try the pegaus driver or comment out the appropriate lines is rc.sysinit.author

[relay]

115,200 fixed the bash. Lots of text ebfore rebooting. I take it there is much more here that a simple #bash prompt.

I need to test which hacks are causing my HDVR2 to reboot after "just a few more seconds" screen. My bash prompt is outputting garbage so I need to put the drive back in my PC.

What mount do I need to do to be able to get access to the rc.sysinit.author file from a PC when I boot using the MFS Tools 2.0 CD? Specifically I want to edit out the network drivers to see if they are the source of my problem. I have tried to look this up but most posts are showing the access from bash prompt which I can't do since I am rebooting constantly.

[Sleeper]

Originally posted by mikand
How do you install additional hacks after using this ISO?

I'm sorry, but that is not a topic for this thread. Please read the other thread's to find out information about specific hacks. You could also post a more specific question like this to the newbie forum.

Bear in mind that certain types of hacks are forbidden to talk about on this site and doing so could jepordize the hard work that is published here. According to forum rules, this includes PM.

[tommy78]

Originally posted by relay

What mount do I need to do to be able to get access to the rc.sysinit.author file from a PC when I boot using the MFS Tools 2.0 CD? Specifically I want to edit out the network drivers to see if they are the source of my problem. I have tried to look this up but most posts are showing the access from bash prompt which I can't do since I am rebooting constantly.

My DSR7000 went into a reboot loop with a kernal panic. Removing the ax8817x driver fixed it.

The rc.sysinit.author was on partition 4 for me, but it is not always the same on different drives. The script detects the root and boot partitions and tells you. Look in the Variables file on your fat32 drive.

Update: I just tried v1.01, it fixes the reboot loop with the ax8817x drivers. Just skip to the hacks phase, takes less than 5 min.

[Sleeper]

tommy,

version 1.01 should fix this problem. Please give it a try.

[billisnow]

Hey Sleeper,

Just wanted to say thanks and nice work!!!
Worked perfectly the first time. I am now watching my monte'd HDVR2. Your utility was very easy to use and took only a few minutes. I really liked the way everything was explained as I went thru it step by step. Makes it alot easier to understand the commands and one of the best things is that I can't make any typing errors to mess myself up :o) Like I did when I did the monte on another one of my boxes Oh well..I guess thats how we learn......

I would also like to thank MrBlack51...Alldeadhomiez...Musclenerd...and all the others who without thier help Sleeper couldn't have made this great utility.

[Sleeper]

Originally posted by billisnow
I would also like to thank MrBlack51...Alldeadhomiez...Musclenerd...and all the others who without thier help Sleeper couldn't have made this great utility.

I'll second that. I meant to thank them too but I've been too busy. And thanks to JJ Bliss for his help, and the many others who are unmentioned that actually devised and explained all the hacks.

Also, many thanks to tommy78, wease and mryuk for hanging in there and helping me figure out why the scripts were not working for them.

I know this is starting to sound like a broken record but thanks to all you guys that posted such kind works. Knowing that it is appreciated makes it all worth while.

Sleeper

[thermal]

Downloaded the 1.0 ISO and attempted to monte the tivo tonight and had some problems. I got a few errors during the restore process:
mfs_read_inode: Inode xxxxx corrupt, trying backup
mfs_read_inode: Inode xxxxxx backup corrupt, giving up

However, it completed saying it was successful, so I completed the rest of the process with no errors.

When I booted up the tivo I get a kernel panic and it restarts:
...
starting rc.sysinit
Releasing /initrd and clearing ramdisk, if they exist
warning: can't open /var/mtab: No such file or directory
Activating swap partitions
Adding Swap: 130044k swap-space (priority -1)
Loading i2c driver
Loading core system drivers
Loading ircatch ...
IRMC registry var is 1 (AVR present).
Loading irblast ...
IRMC registry var is 1 (AVR present). irblast not loading.
/lib/modules/irblast.o: init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including invs
Checking for Kickstart panic signal
/etc/rc.d/rc.sysinit: /tvbin/checkpanic-asic: cannot execute binary file
Found rev '' P2109-V90 modem on /dev/cua1
Kickstart entered with code 126
Unknown panic code - no action
Restarting system.

1.) What model is your unit?
TCD140060 - SA

2.) How big is the original hard drive?
60GB

3.) Is or has your original hard drive been hacked before.
No

4.) Have you ever performed a mfsrestore to your original hard drive?
No

5.) What version of software is running on your original hard drive?
4.01

6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?
Not DTivo

7.) What size is the drive that your are restoring to?
Seagate 80gb

8.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.
During clean-up phase of restore
mfs_read_inode: Inode xxxxx corrupt, trying backup
mfs_read_inode: Inode xxxxxx backup corrupt, giving up

9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.
...
Checking for Kickstart panic signal
/etc/rc.d/rc.sysinit: /tvbin/checkpanic-asic: cannot execute binary file
Found rev '' P2109-V90 modem on /dev/cua1
Kickstart entered with code 126
Unknown panic code - no action
Restarting system.

See above also

10.) Did you spill coffee on your Tivo while you had it open? Just kidding?

11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?
Did not test after restore phase - probably should have

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?
Ran through the whole process before testing

Thoughts?

[wease]

After all the effort Sleeper put into the lasted version i'm happy to announce that every thing works.I was one of the lucky few that worked with Sleeper trying his method's and finnally we are working.This is with the original drive which was a problem before but no longer.Everyone with interest in Tivo should thank Sleeper as he has made it easy for all us non linux people understand how it works.
Thanks again Sleeper

[Sleeper]

Thoughts?

Thanks for providing all the necessary info and being honest about it.

11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?
Did not test after restore phase - probably should have

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?
Ran through the whole process before testing

It looks like a bad mfsbackup. Thankfully, you have the original drive and were not trying this on the original drive.

Start over again, you need a clean backup.

Test the drive in the TIvo after each of the 3 phases, RESTORE, SURGERY and FINAL.

Also, please be aware of the network problems in release 1.0. Do not use ax8817x driver. Also problem with SA units. Both problems are fixed in version 1.01 and are being tested now.

[Sleeper]

Originally posted by wease
After all the effort Sleeper put into the lasted version i'm happy to announce that every thing works.I was one of the lucky few that worked with Sleeper trying his method's and finnally we are working.This is with the original drive which was a problem before but no longer.Everyone with interest in Tivo should thank Sleeper as he has made it easy for all us non linux people understand how it works.
Thanks again Sleeper

Your Welcome!

Not only did you monte your original drive, but the unit is running 3.10 software and was not yet subscribed.

I also have had success duplicating the original drive and testing the scripts on an unsubbed (out of the box) unit.

Of course, updating to the latest software and subbing the box are still recommended and using another drive is HIGHLY recommended.

I mention this becasue others have asked me if the scripts would work on a unit right out of the box.

[honormeall]

[QUOTE]Originally posted by Sleeper
[B]



Is the beta site for 1.01 for public use?? IF not when do you expect to release it. I will need the updated fix for the ethernet config.

Thanks again sleeper for all your hard work. :D

David


Edited to remove link to script. Script can be located in the first post of this thread.


Sorry for the prolem sleeper just got excited there for a minute.

david

[bzo]

I am happy to confirm that the ax8817x seems to be fixed in the 1.01 release. This is on a HDVR2/3.1.0 system.

Like most other folks, the scripts worked perfectly for me. The only snafu I ran into was that during the "surgery" phase, I had some read errors. Ends up that I had a bad burn from the iso to a cd - reburning at a slower speed cleared up the problem.

Thanks to sleeper for a great utilty!

[Sleeper]

Is the beta site for 1.01 for public use?? IF not when do you expect to release it. I will need the updated fix for the ethernet config.

No it is not for public use.

Everybody please stop PM'ing me. I can't get anything done if I have to keep emptying my inbox.

Also, please stop PM'ing the beta testers that know the site. If this keeps up I will take the site down. It's for people testing.

If you are interested in a new feature, post your interest in the thread. The thread is permanent storage. My PM inbox is not. If you have reported a NEW bug to the thread or have posted interest in a new feature, then I will PM you about testing the next beta release.

I'm sorry that I have to take this posture but this has gotten out of control!

Check the first post in the thread. It will probably be up tonight or early tommorow.

Thanks again sleeper for all your hard work. :D

YOUR WELCOME!

David,

Please edit you previous post and remove the link. It will not update whem I update the latest release and could cause some problems. Thanks

[MiamiTV]

Let me tell you all about SLEEPER, This guy is the BEST. He has put together a Stupid Proof ( ME ) way to upgrade your Series 2 TiVo. I spent 3 days trying to do this by my self, and In 20 Min. with SLEEPER's ISO BAM!!!! I was up and running.


Thank you so mush for the countless hours you have spent making life easy for the rooks out there that need step by step guidence.


Thanks Again.

[Meathead]

I can't get past the "Welcome. Powering up..." screen. I have 2 brand new Series 2's. An HDVR2 and a DSR7000.

1.) What model is your unit?
HDVR2

2.) How big is the original hard drive?
40GB

3.) Is or has your original hard drive been hacked before.
No

4.) Have you ever performed a mfsrestore to your original hard
drive?
No

5.) What version of software is running on your original hard drive?
3.1 pending restart

6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?
DTV Sub. Tivo, not yet

7.) What size is the drive that your are restoring to?
120GB Seagate

8.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.
None

9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.
n/a

10.) Did you spill coffee on your Tivo while you had it open? Just kidding?
Nope

11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?
Yes, and it did work. I can't get past the surgery phase.

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?
Can't get that far.

I tried 2 different computers, 2 different 120GB drives, and even a brand new "virgin DSR7000".

I forced a call on the HDVR2 and backed it up "pending restart". I have tried at least 10-15 times to get this to work. Any help would really be appreciated.

Thanks,
Meathead

[Sleeper]

Originally posted by Meathead
12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?

Can't get that far.



You need to get a serial cable and terminal program hooked up and capture the output.

Also, start with RESTORE and SURGERY.

STOP after SURGERY and test drive. Capture output from serial port and post error.

Also, make sure you are using version 1.01 Earlier versions had a bug with ax8817x network drivers that caused a problem.

Sleeper

[relay]

Sleeper, you da man!!!!!!!!!!
V.1.01 worked on first try!!!!!!! My issue was the network drivers in 1.0.
This is the best tool for those that just want to get watching TV and not playing around with their Tivo for days on end!!!!!

Perhaps I can give something back to you and the community. If you need a host for the ISO file I would be glad to help out. I might throw up an image of 3.1b as well since so many are looking for it (:

A couple of suggestions:
1st, perhaps a break out of the script after the surgery phase so that a user could test out the bash and verify that it was working BEFORE the hacks installation. THis would help for diags. It would also allow users to pick up where they left off whereas right now they have to restart the script from scratch.

2nd, a confirmation at the end telling the user that the script has completed so that they don't have to guess if it's all done. I know, should be able to figure it out but you are targeting some non tech. people with this ISO.

3rd, perhaps a method to start at the restore phase using the already created .mfs file. This would allow a user to bypass the backup phase when something did not work right related to the restore. I must have done dozens of the full process while trying to get a pair of 160GB drives to work. Had to give up and go with a pair of 120's.

[Spydertech]

I used Sleepers script to test something out last night.

I loaded a SA 4.0 on a HDVR2 original drive - had to run clear and delete.... no problems.

I then used the script (1.01) to perform the monte hack (as if it were still a stand alone unit).
Just a couple of things I noticed - I don't think any of it is related to the script though.

I had a USB wired adapter plugged into a wireless bridge and the network settings screen showed the IP for the bridge (not the one I setup in the rc.sysinit.author) but I think it is just a quirk of the SA software (since the IP I used in the rc.sysinit.author is the one that actually works).

The fixsub didn't seem to work the same - it originally showed a successful call on Dec 18, with the next scheduled call on Sept 8, but it did show as Successful.....

And of course (as has been noted before) Tivoweb doesn't work...

Just some observations.

The script works great!

Spydertech

[Meathead]

Yes, I am a Meathead! I was running the script from the "P" Prom menu choice. I don't have a hacked Prom. I needed to try it from "M" for Monte. Now it works great. Thanks to Sleeper for helping me discover my error. And thanks to all the others who made this possible.

Thank you,

Meathead

[Sleeper]

Originally posted by Spydertech
The fixsub didn't seem to work the same - it originally showed a successful call on Dec 18, with the next scheduled call on Sept 8, but it did show as Successful.....

You may want to periodically check the fixsub.log file in /var/hack/log/fixsub.log

An entry is made everytime the script runs.

And of course (as has been noted before) Tivoweb doesn't work...

Yea, that's a bummer. I hope someone comes up with a fix. It's really a great program!

The script works great!

Thanks!

[midnightmaraude]

I've read the thread here 3 times... my main question is as follows:

I have a brand new HDVR2 which I haven't even opened up yet. I'm assuming it has 3.1 software on it. I haven't even powered it up. I'm hearing about the 3.1b which i'm assuming is the latest OS for the Dtivo series2? My question is... my HDVR2 is not subbed and we do not have a phone line (use cell phones instead) So as silly as this question sounds, can I backup using 1.01, restore onto 120gig drive , put back in tivo force a daily call and have the software upgraded via satellite? Or do I NEED A PHONE line in and does the machine have to be subbed?


I appreciate the assistance.

[relay]

I think your going to need a phone line, at least for the basic test call and a few daily calls. Bring it to a friends house if need be. You should be able to do it inside of a day or so. It does not need to be setup or subbed for the test call or a daily call.

Easiest way is to let the factory drive upgrade to 3.1b and then use this script if it's released to public.
Do a basic setup. Configure the test call and then tell it to do a daily call. It too me trying on and off over 2 days to get it to download 3.1b. From what I am told the upgrade process is going by serial # and if your unit is not on the list then your not goin to get it.

[JJBliss]

When choosing option (M) for Monte, and then (a) for backup, why are you not backing up the Series 2 with mfsbackup -f 9999 ... as Hinsdale recommends instead of mfsbackup -f 4138 ...

Doesn't not doing this cause the see through menu problem?

[Mighty LoPan]

Sleeper, in case you haven't heard it enough yet, your setup disk kicks ass. I was up and running in like 15 minutes. Thanks!

[captain_video]

I finally got the chance to try out your program this evening. I must say I am quite impressed. You have put together one of the most comprehensive hacking programs I have seen yet in this forum. The informational prompts at each step are a real plus. The only thing I can see that would make it even better would be a companion guide that explains each step in more detail outlining what's actually happening behind the scenes. It would be kind of like the bonus DVD in a boxed set with the behind the scenes footage and outtakes.

I ran into the same pitfall that someone else posted earlier in that I mistakenly chose the PROM option the first time through. I wasn't thinking clearly and it became quickly apparent that I had made the wrong choice when I tried to boot the Tivo with the "hacked" drive. When I realized my mistake I sailed right through the installation process and everything worked as advertised when I was finished. You may want to indicate that the PROM option is for hacked PROMs only, although most people that aren't half brain dead should be able to figure that one for themselves. What can I say, I had a long day at work.

My compliments on a truly outstanding effort.

[relay]

Sleeper: Perhaps the Prom option should be the 2nd option and the 1st should be Monte as this would be a lot more prevelant. In such a small test group you already have a few mistakes of the sort it mike make sense before releasing to the world....

[digitaloutlaw]

I just ran the script, and had my unit running in about 30 mins! I swapped the original 40GB for a 120GB.. still have to try to get the drivers working for my Linksys WUSB11 - and just realized the serial cable I bought has a male end.. need a gender changer tomorrow.. I was totally stuck with cobelli's guide (since some of the steps left out some details on Linux and on file names, etc..) I'm so happy that Sleeper mentioned his iso, or I would have been sitting here pulling my hair out! Thanks for your hard work Sleeper!

Tomorrow I will venture with some other hacks, and try to have some fun with my DSR7000!

Thanks again!

DO..

[Tux Man]

Originally posted by relay
Sleeper: Perhaps the Prom option should be the 2nd option and the 1st should be Monte as this would be a lot more prevelant. In such a small test group you already have a few mistakes of the sort it mike make sense before releasing to the world....

haha ya make it so they just have to hit enter, and it works..

If they have to think about it they might learn something.

Tux

[Sleeper]

Originally posted by midnightmaraude
My question is... my HDVR2 is not subbed and we do not have a phone line (use cell phones instead) So as silly as this question sounds, can I backup using 1.01, restore onto 120gig drive , put back in tivo force a daily call and have the software upgraded via satellite? Or do I NEED A PHONE line in and does the machine have to be subbed?

That's a run-on question if I ever saw one.

Here are the multiple answers.

1) The tivo does not have to be subbed, you could perform all the phases but all your ever going to have is 3.1. Supposedly 3.1b fixes an audio problem that I never experienced. Other than that I do not know of any benefit to 3.1b.

2.) You could do just a backup and restore to the larger drive and everything should work. The box will eventually get upgraded and operate just fine.

2) You MAY be able to plug the unit in and force an upgrade without being subbed.

[Sleeper]

Originally posted by JJBliss
When choosing option (M) for Monte, and then (a) for backup, why are you not backing up the Series 2 with mfsbackup -f 9999 ... as Hinsdale recommends instead of mfsbackup -f 4138 ...

Well, that's a very interesting question that I pondered upon when I wrote the script. There has been talk of loosing the see through menus with the -f 4138 option. I have not experienced it and so far no one that has used the scripts has reported it.

My understanding is that the -f 9999 option does not backup everything, just streams with a fsid <= 9999.

I believe that the -a option backs up everything.

I chose to use the -f 4138 because I believe that most peolpe will want to keep the noscramble hack in tact and will loose their recordings anyway.

The next major release will have more options.

Please correct me if my interpertation of mfsbackup is incorrect.

[Sleeper]

Originally posted by captain_video
The only thing I can see that would make it even better would be a companion guide that explains each step in more detail outlining what's actually happening behind the scenes. It would be kind of like the bonus DVD in a boxed set with the behind the scenes footage and outtakes.

Actually, I thought about writing one, but there are only so many hours in the day - and right after I started this thread I got really hammered with PM's. Thank god things have finally quieted down.

What I was thinking about doing in very lay man's terms is explaining about how the tivo and monte work without all the unix stuff. The problem with most of the howto's (no offense) is that a non-unix person doesn't have a clue what all the dd, mount, genroms, etc are doing. So it would make it easier for them to explain it without all the tedious details.

Then they could run the scripts and learn all the detail.

I ran into the same pitfall that someone else posted earlier in that I mistakenly chose the PROM option the first time through.

Another honest admission. I will definately change this in the next version. You are the 3rd person that admitted this. I wonder how many others have done it and did not admit it.

My compliments on a truly outstanding effort.
Thank you!

[Sleeper]

Originally posted by relay
A couple of suggestions:
1st, perhaps a break out of the script after the surgery phase so that a user could test out the bash and verify that it was working BEFORE the hacks installation

Yes!

2nd, a confirmation at the end telling the user that the script has completed so that they don't have to guess if it's all done. I know, should be able to figure it out but you are targeting some non tech. people with this ISO.

Yes!

3rd, perhaps a method to start at the restore phase using the already created .mfs file.

Yes Again! However, you can skip any of the phases if you pay attention and hit any key other than enter at the appropriate time. I understand the suggestion.

All of these these are great suggestions that I will incorporate into the next major release.

Also, I will be doing auto detect of the version of sortware that the tivo is running so to be able to install customized hacks for your version.

Also, I will support backing up a monte'd drive.

Restoring any image for those who want to use 3.1b or 4.x.

Un monte-ing a monte'd installation in order to let an upgrade occur.

Please keep the suggestions coming

[wease]

Off to Cancun and can't wait to see the changes you make when i get back.(not really.Cancun or Canada.NO real choice there,sun and warm or chance of snow)
Will chat when i get back and keep up the good work.

[dogbreath]

I am installing monte on an HDVR2 with 4.0 os from a SAS2. A kernel panic occurs when the usb modules "usbcore.o" try to load. I get a message that the modules are compiled for the 2.4.4 kernel and not the 2.4.18 kernel.

dogbreath

[Spydertech]

If you are installing the Stand Alone OS - treat the unit like a Stand Alone and DO NOT install the network drivers (they are already there....)

Spydertech

[dogbreath]

I commented the drivers out in the rc.sysinit.author and the drivers still try to load and the kernel panics. Any ideas?

dogbreath

[Spydertech]

What I meant was - when you apply the monte hack - treat the unit as a Stand Alone and answer the questions as such....

The problem is that you replaced the SA network drivers with the ones for the HDVR2 software - and obviously that won't work.

Re-do the monte using the 1.01 script - and answer all the question as if it was a stand-alone unit.

Spydertech

[Sleeper]

Originally posted by dogbreath
I am installing monte on an HDVR2 with 4.0 os from a SAS2. A kernel panic occurs when the usb modules "usbcore.o" try to load. I get a message that the modules are compiled for the 2.4.4 kernel and not the 2.4.18 kernel.

dogbreath

Yes, that will happen. There are several ongoing threads about this topic. This is not currently supported by the scripts.

Please move this topic to another thread.

[digitaloutlaw]

Hey Sleeper.. I followed your iso, and had no error on my DSR7000.. I see that it shows Successful to the call - and I'm assuming that it means that the scripts are running. I'm trying to connect with a serial bash now.. and I'm not getting anywhere. Is there something that I need to do different? (I'm connecting with Hyperterm, N,8,1, Hardware flow control). I'm getting nothing appearing in my term window at all.

[midnightmaraude]

Digital
connect to the baud rate that starts with 115 i believe.. and turn flow control off



My question: I'm downloading s2-40-4-0b.bak from tivostuff.. it came from a TCD240040 series 2 standalone unit 40 hour.

Will this backup work using sleepers iso? I want to put it on a HDVR2

[dogbreath]

midnight

It works just fine on an HDVR2

dogbreath

[Sleeper]

short the two outer pins of the 1/8" connector together. Type at your terminal. The characters should be echoed. If that works, try using a null modem - you may have TX & RX reversed. Here is one of the many post on how to construct a cable:

http://www.dealdatabase.com/forum/showthread.php?s=&postid=16187&highlight=make+serial+cable#post16187

[Sleeper]

Originally posted by midnightmaraude
Digital
My question: I'm downloading s2-40-4-0b.bak from tivostuff.. it came from a TCD240040 series 2 standalone unit 40 hour.

Will this backup work using sleepers iso? I want to put it on a HDVR2

Originally posted by Sleeper
Yes, that will happen. There are several ongoing threads about this topic. This is not currently supported by the scripts.

Please move this topic to another thread.

WHICH WORDS IN THE ENGLISH LANGUAGE DON'T YOU UNDERSTAND? I WILL SEND YOU A LINK TO AN ONLINE DICTIONARY

TAKE THIS DISCUSSION ELSEWHERE! FOR THE LAST TIME, IT IS NOT CURRENTLY SUPPORTED

[creepy]

Sleeper thanks for all your work on this! I did mine last night and everything went very well.

I do have one observation and maybe it's only happening to me. Five minutes after I reboot I notice the Tivo starts changing screens and jumping from screen to screen. I noticed the sleep 300 in the .author file and assume it's the fixsub that is causing this. Is this normal?

[midnightmaraude]

Sleeper don't jump to conclusions that i"m a noob man. I was simply asking about a specific TiVo from which the image came from. I know 4.0 will work on a HDVR2 but wanted to make sure the one I was downloading would suffice.

[digitaloutlaw]

Thanks again Sleeper! The cable I bought on eBay must have been config'd wrong. I sliced and spliced and can see data now. I can see all the boot up data - I've waited about 5 mins, and got:

rc.sysint is complete
00:10:00 - ping - mfs_ftp running on 127,0,0,1 : 3150
00:15:00 - pong - mfs_ftp running on 127,0,0,1 : 3150
00:15:00 - entering update_rec_fsids
00:15:00 - getting current_rec_fsids list
00:15:00 - new/old lists match - no update necessary

Should I be seeing a prompt somewhere here? Sorry for the dumb questions.. but I've search already, and posted in the newbie section.. and haven't gotten and replies yet.

[Sleeper]

Originally posted by creepy
Sleeper thanks for all your work on this! I did mine last night and everything went very well.

I do have one observation and maybe it's only happening to me. Five minutes after I reboot I notice the Tivo starts changing screens and jumping from screen to screen. I noticed the sleep 300 in the .author file and assume it's the fixsub that is causing this. Is this normal?

I was wondering when someone would bring that up.

It is the 30 second skip and Now Playing Sort option scripts being executed.

The next release will have the 30 second skip tivoapp patch. If someone comes out with a direct patch for kmem and directory sort I will incorporate them also.

[JJBliss]

Originally posted by midnightmaraude
Sleeper don't jump to conclusions that i"m a noob man. I was simply asking about a specific TiVo from which the image came from. I know 4.0 will work on a HDVR2 but wanted to make sure the one I was downloading would suffice.

Be very careful mignightmaraude, we haven't forgotten who you are.

You're past still haunts you.

You are most definitely still a noob. The amount of time since your registered in no way promotes you to other then noob status.

Sleeper has said that his ISO does not support 4.0 SA software on the HDVR2. For now, that's gospel. Do not include discussions in this thread that are not supported by the provider of the software.

[Andy in NYC]

Yet Another Question:

Edited to ask the better question <g>.

The script states that the restore will expand to multiple drives. The documentation doesn't tell me where to put the new Tivo B drive. I'll try Secondary Slave, but perhaps the initial text could elaborate for others like me who are doing the full monte with a pair of drives.

Thanks so much.

Andy

[Sleeper]

Andy,

Good questions. This has been untested but theoretically, it should work. I coded for it just never tested it.

Run scripts, Do backup of original drive. Attach both new drives on the secondary controller, master and slave. (/dev/hdc, /dev/hdd). Do the RESTORE phase - it should detect the 2nd drive. After the RESTORE and BEFORE SURGERY, test both drives in the Tivo. If everything works, just put the master drive in your pc and perform the SURGERY and FINAL phases.

Please let me know if this works.

[knot]

Sleeper - AMAZING - thanks for all your work! I was up and running in no time. You got me further in 15 minutes than a whole day of trial and error and error.

Suggestions:
Sorry if these are very newbie...

1. A way to designate which drive is your cd-rom, tivo-a and tivo-b. Sounds like whining, but my cables do not reach well in this configuration.

2. A readable text dump of the text output of your script so that it can be printed (I could not find a ReadMe with everything on the CD).

[BiggJ]

Originally posted by Sleeper

To use them you download the ISO, burn the disk and boot from it. You must install a FAT32 drive as Primary Master, a bootable CD drive as Primary Slave and the Tivo drive as Secondary Master.


Why FAT32 partition? I have a ext2 or ext3 available, but no FAT32? Do you just say FAT32 because NTFS won't work? In which case ext2/3 would work, right?

--BiggJ

[Sleeper]

Originally posted by BiggJ
Why FAT32 partition? I have a ext2 or ext3 available, but no FAT32? Do you just say FAT32 because NTFS won't work? In which case ext2/3 would work, right?
--BiggJ

Wrong! If you read the mount command before you press enter you will see the "-t vfat" option.

Future versions may allow ext2/ext3. and, as previously suggested, hooking your drives up differently. For now it operates the way that it is documented.

FAT32 because that is what MOST people are using. No other reason.

[digitaloutlaw]

Hey Sleeper.. I've loaded your ISO 3 times.. thinking that I may have done something wrong.. but everything seems to check out. The problem is that I am not gettng a bash prompt. I'm using a dsr7000 and hyperterm. I can see all the data coming on my laptop when I reboot the dtivo.

Am I missing something? From what I've been reading I should get a bash prompt after hitting enter. Do I need to do anything else in order to get a bash prompt?

please help
:(

[BiggJ]

Okay, cool, good to know.

I'd like to look into hacking the script and recreating the iso. I copied the contents into a tmp dir and grep'd for "t vfat" with nothing returned (outside of the hackfaq.htm). Would you mind pointing me in the right direction?

--BiggJ

[Andy in NYC]

I'm on my fourth version of running the scripts

Times 1 and 2 it found both drives, I gave it the IP info and it came up as a 200+ hour machine. I could telnet in.

First time, I also got random bouncing among the menu pages - I remember seeing something about this, but couldn't find anything on my search

Entering the ,#401 command gave me a dialing error - it was still looking for my phone line.

3rd time it didn't see the second 120 GB drive and also didn't 'take' the usb adaptor

Parts of my HDVR2/network

Linksys 200M adapter
Netgear router

Netgear set at 192.168.0.1
Setting Tivo at 192.168.0.10
Broadcast as 192.168.0.255
mask at 255.255.255.0
gateway as 192.168.0.1

Linksys 200M uses the A) choice of drivers (aix...) not the Pegasys

So, what am I doing wrong?

Help before my wife kills me dead!

Andy

[midnightmaraude]

Lets not start that up again. the file was released yes,, did anything happen... no! I'm not a noob... been doing tivos long before ddb was created.

Originally posted by JJBliss
Be very careful mignightmaraude, we haven't forgotten who you are.

You're past still haunts you.

You are most definitely still a noob. The amount of time since your registered in no way promotes you to other then noob status.

Sleeper has said that his ISO does not support 4.0 SA software on the HDVR2. For now, that's gospel. Do not include discussions in this thread that are not supported by the provider of the software.

[Sleeper]

Andy,

I have not tested the scripts with 2 drives so I can not confirm/deny that it works. In theory it should.

I suggest that you get one drive up and running from a restore. Don't do any SURGERY or HACKS. Then manually add the second drive. See if you can get both drives running in the tivo.

After both drives are running, put the master back in the PC and run the SURGERY and FINAL phases.

[Sleeper]

midnightmaraude

I don't know who you are. I don't care. You are welcome here as long as you stay on topic. Please take the other stuff to another thread, PM or start a new thread.

Thanks,

Sleeper

[txag93]

1.) What model is your unit?
HDVR2
2.) How big is the original hard drive?
40G
3.) Is or has your original hard drive been hacked before.
NO
4.) Have you ever performed a mfsrestore to your original hard drive?
NO
5.) What version of software is running on your original hard drive?
3.1b? (latest, it just got it via phone line today)
6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?
Yes, yes, yes
7.) What size is the drive that your are restoring to?
120G
8.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.
Stuck on mfsrestore command at 67 blocks of 1441 (4.X%)
9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.
no error reported, gets stuck on mfsrestore. BIOS sees drive as 120GB ST3120...
10.) Did you spill coffee on your Tivo while you had it open? Just kidding?
nope, :-)
11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?
Can't get restore phase to work.
12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?

FIXED by getting a different FAT32 drive and starting over. I couldn't rename or rmdir the TIVO directory, kept complaining about being mounted read only, tried chmod, etc. Finally gave up and grabbed another drive.

Working good now.

[Sleeper]

txag93,

Thanks for the detail.
Here are my guesses.

1.) Bad backup for some reason. Try renaming the tivo directory on your cdrive and start again.

2.) Problem with drive being restored to. Try wiping the drive.

3.) Bad burn of the ISO. 2 people reported problems that were caused from a bad burn.

I thought you used the scripts successfully once before.

Sleeper

[ShanClarke]

Sleeper,
Thank you so much. This is a wonderful tool. I spent severl hours last week trying to get my DTivo up on my home network and after only a few minutes with your tool I was up and running.

Thank You you did an awsome job

[txag93]

Sleeper, thanks for the quick reply. This was my first use of your script.

FIXED by getting a different FAT32 drive and starting over. I couldn't rename or rmdir the TIVO directory, kept complaining about being mounted read only, tried chmod, etc. Finally gave up and grabbed another drive.

Working good now.

Great script. I assume if I had scrambled recordings on the drive prior to running this script that they can be deleted by doing a clear and delete everything? I want to capture that space for future recordings. Just making sure clear and delete everything AFTER surgery phase won't wipe things out. I am pretty sure it won't.

[creepy]

This script is super! I did two tivos and both were successful, although one has problems with tivoweb, but not a big deal. The last one I did will not show the graphical remote control. I don't know what the difference could be and I didn't receive any errors during the install on either Tivo.

I did notice a glitch when the script says that it is appending to the .author file during the last phase of the install, it said that it is is adding "#Waiting for sat data" or something similiar. That never gets appended to the file. Doesn't affect anything, but just thought I'd bring it up in case you wanted to fix that.

Thanks again Sleeper for all you efforts!!!!!

[nikunjs]

Just tried it on a DSR7000 and works like a charm!

Thanks a bunch

[thermal]

Finally got hacked tivo up with 1.01 script! I think the 80gb drive I was using may have been bad.

Anyway, I have now having a different problem. No errors during any phase of the script - installed all the hacks, the hacked drive is up bash is working, ethernet is working.

However, when I record a show it will not playback.

In /var/log/tverr log I see the following every time I try to play a newly recorded show (these recording took place on the hacked tivo - not the original):

Nov 9 17:53:47 (none) pcache[151]: Encryption mismatch.
Nov 9 17:53:47 (none) TmkMultiMpegClip::Trace[151]: Setup(753790) Status:262145
Nov 9 17:53:47 (none) mediamgr[151]: 0x40001 at line 2322(mmguts.C)
Nov 9 17:53:47 (none) mediamgr[151]: 0x40001 at line 1306(mmguts.C)

See below for your troubleshooting questions:

1.) What model is your unit?
TCD140060 - SA2

2.) How big is the original hard drive?
60GB

3.) Is or has your original hard drive been hacked before.
No

4.) Have you ever performed a mfsrestore to your original hard drive?
No

5.) What version of software is running on your original hard drive?
4.01

6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?
Not DTivo

7.) What size is the drive that your are restoring to?
New WD 60gb

8.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.
Nope

9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.
See above tverr log

10.) Did you spill coffee on your Tivo while you had it open? Just kidding?

11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?
Tested boot after each phase - successful

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?
Tested boot after each phase - successful

Thoughts? :)

[NutKase]

Originally posted by thermal
However, when I record a show it will not playback.

In /var/log/tverr log I see the following every time I try to play a newly recorded show (these recording took place on the hacked tivo - not the original):

I've never ran Sleeper's script. Does it patch the tivoapp? If you're running kmem or a kernel patched to record uncrambled you will have to also patch tivoapp to view it.

The patch address for 4.01 was one of the few things I've been able to contribute so just search for it if you think you need it.

NutKase

[Andy in NYC]

1.) What model is your unit?
HDVR2

2.) How big is the original hard drive?
35 hour

3.) Is or has your original hard drive been hacked before.
Original


4.) Have you ever performed a mfsrestore to your original hard drive?
No

5.) What version of software is running on your original hard drive?
3.1.1b

6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?
yes and yes

7.) What size is the drive that your are restoring to?
2 x 120 GB

8.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.
No

9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.
No error

10.) Did you spill coffee on your Tivo while you had it open? Just kidding?
I only spill soda on my keyboards and myself

11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?
No, but Tivo was working fine

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?
No, but Tivo was working fine

The error is that the Tivo won't respond to my remote or to button pushes on the Tivo itself. It was recording on at least one channel at the time.

[digitaloutlaw]

Originally posted by Andy in NYC
The error is that the Tivo won't respond to my remote or to button pushes on the Tivo itself. It was recording on at least one channel at the time.

Did you double check your remote cable? When I first got my Tivo shipped to me, I had the same problem. When I opened it, I noticed the white ribbon remote cable wasn't seated. I reseated (while the power was unplugged of course) and it was fine. If you powered on your Tivo, and the cable wasn't seated properly, you may have fried your remote daughter board. Bummer.

[Sleeper]

Originally posted by Andy in NYC
The error is that the Tivo won't respond to my remote or to button pushes on the Tivo itself. It was recording on at least one channel at the time.

If the remote control & front panel are not working at all, then there is a good chance your ribbon cable was loose or not plugged in all the way. Power down the unit and check the cable. Many units have been fried do to this.

Also, put your original drive back in and see if it works.

[Sleeper]

Originally posted by NutKase
The patch address for 4.01 was one of the few things I've been able to contribute so just search for it if you think you need it.NutKase

Nutkase, I am just installing kmem. Different kmem parameters for a SA versus DTivo. I was not aware that you had to patch tivoapp as well as kmen or kernel patch on the SA units. For those reading this you do not have to patch tivoapp for a 3.x version tivo only standalone units. Is this true for both 4.0 and 4.01 units? I will incorporate the patch into the next release. It's curious that that no other SA unit owners have reported ths.

[mrblack51]

Originally posted by Sleeper
Nutkase, I am just installing kmem. Different kmem parameters for a SA versus DTivo. I was not aware that you had to patch tivoapp as well as kmen or kernel patch on the SA units. For those reading this you do not have to patch tivoapp for a 3.x version tivo only standalone units. Is this true for both 4.0 and 4.01 units? I will incorporate the patch into the next release. It's curious that that no other SA unit owners have reported ths.

as of version 4.x, tivoapp has a check for scrambling. as such, to do noscramble, you need to patch tivoapp and do the kernel patch. 3.x units didnt do it. i would imagine that if 4.x ever hits the s2 dtivos, it will have the same stuff. of course, that will be when the s2 dtivos get HMO i imagine

[Andy in NYC]

I powered down and powered up w/out checking the cable.

The remote now works fine.

On bootup, the Tivo still seems to be randomly jumping through menus (as though buttons had been pushed). This then goes away by itself. I would love to know what causes this.

Andy

[Sleeper]

tivoapp needs patching on 4.x
A little searching found it here:

http://www.dealdatabase.com/forum/showthread.php?s=&postid=112847&highlight=kernel+patch+enough#post112847

I guess tivo got wise to the kernel patch.

[Sleeper]

Originally posted by Andy in NYC
On bootup, the Tivo still seems to be randomly jumping through menus (as though buttons had been pushed). This then goes away by itself. I would love to know what causes this.
Andy

That is the SPS30 and directory sort scripts running. If you don't want them comment tnem out in your rc.sysinit.author file.

[Andy in NYC]

As you know by now, I have a HDVR3 with .b running. What part(s) of TivoWeb don't work - it seems to be running just fine after my cursory testing.

Since my Tivo still seems to search for a dial tone after I make the ,#401 pre-fix, how will it 'call home' if I order pay per view, etc.? Is this failure by design, or am I missing something. The error is 'no dial tone'.


Andy

[NutKase]

Originally posted by Sleeper
For those reading this you do not have to patch tivoapp for a 3.x version tivo only standalone units. Is this true for both 4.0 and 4.01 units?

It's a software version issue. No matter what unit it goes on, 4.0 and 4.01 will have to have the tivoapp patched.

The patch is different for each version and posted already on DDB as you've probably found by now.

NutKase

[Buckeyes1995]

The script is quite impressive, but I have the same problem.. in Hyperterm I can see the bootup, but can't actually get a bash prompt. Any ideas?

Thanks,

Jim

Originally posted by digitaloutlaw
Hey Sleeper.. I've loaded your ISO 3 times.. thinking that I may have done something wrong.. but everything seems to check out. The problem is that I am not gettng a bash prompt. I'm using a dsr7000 and hyperterm. I can see all the data coming on my laptop when I reboot the dtivo.

Am I missing something? From what I've been reading I should get a bash prompt after hitting enter. Do I need to do anything else in order to get a bash prompt?

please help
:(

[NutKase]

Originally posted by Buckeyes1995
I can see the bootup, but can't actually get a bash prompt. Any ideas?

One of you post your output from the serial session (hopefully in a .txt attachment :)) We need more info.

NutKase

[MHarhen]

This script is great - worked first time!

I was able to upgrade from 40 hr/40 MB to 120MB + 160MB in one step.

Some additional info:

1. The tivoapp patch is required for 4.0.1. It 4.0.1 patch also works on 4.0.1a

2. To make the joe editor work, do the following:
a) mkdir /var/hack/etc
b) cp /etc/joerc /var/hack/etc/joerc
c) cp /etc/rjoerc /var/hack/etc/rjoerc

3. /etc/rc.d/rc.sysinit.author has been modified to set the IP address. This interferes with version 4.0.1's ability to set the IP address using DHCP. I suggest that for version 4.0.1 (possible 4.0?) the calls to "ifconfig" and "route add" are unnecessary and should be removed.

[MHarhen]

Bash problem?

I have not experienced the bash problem reported by some users. However I have noticed that sometimes the bash prompt using telnet does not appear immediately. However it finally appears after hitting the return key 5-10 times.

[NutKase]

Originally posted by MHarhen
1. The tivoapp patch is required for 4.0.1. It 4.0.1 patch also works on 4.0.1a

What exactly is 4.01a?

Where did you get it?

As far as I know, not even SA S2 tivos have such a thing.

NutKase

[EDIT] OK, it appears that 4.01a is a beta release designed to add a couple of wireless adapters to the 'working' list. the WUSB11 with 2.8 firmware for instance.

[digitaloutlaw]

Originally posted by NutKase
One of you post your output from the serial session (hopefully in a .txt attachment :)) We need more info.

NutKase

Here you go.. like I said.. no errors at all when I ran Sleeper's iso.. just can't get bash.

thanks.. your help is appreciated Greatly!

DO.

[MHarhen]

Re: version 4.0.1a:

See Tivo Community (http://www.tivocommunity.com/tivo-vb/showthread.php?s=&threadid=140062)

[NutKase]

Originally posted by digitaloutlaw
Here you go.. like I said.. no errors at all when I ran Sleeper's iso.. just can't get bash.

thanks.. your help is appreciated Greatly!

DO.

It appears by the log that you're booting the 3.0 kernel then monte'ing successfully into... ...the 3.0 kernel again.?.

Are you sure your have a more current kernel in the partition you're monte'ing TO?

How are you calling /bin/bash?

NutKase

[digitaloutlaw]

Originally posted by NutKase
It appears by the log that you're booting the 3.0 kernel then monte'ing successfully into... ...the 3.0 kernel again.?.

Are you sure your have a more current kernel in the partition you're monte'ing TO?

How are you calling /bin/bash?

NutKase

This is all from using Sleeper's ISO to image a new 120GB in my DSR7000. I have edited or been able to change anything.. since I can't bash. I thought the iso did everything for you - sleeper says it loads all the scripts for you. Any comments on this Sleeper? Is there another step after the image is restored and rebooted? When the load was all completed, it went back to the main page where you choose prom or monte.

[NutKase]

Originally posted by MHarhen
I suggest that for version 4.0.1 (possible 4.0?) the calls to "ifconfig" and "route add" are unnecessary and should be removed.

Exactly, 4.0 and above software versions don't need 'networking' commands like ifconfig/route add or nicdrivers.o additions.

You do have to remember to 'disable' the netfilters entries in rc.sysinit however.

NutKase

[Sleeper]

Originally posted by MHarhen
This script is great - worked first time!

To make the joe editor work, do the following:
a) mkdir /var/hack/etc
b) cp /etc/joerc /var/hack/etc/joerc
c) cp /etc/rjoerc /var/hack/etc/rjoerc

Although that works, its not really a great way to do it. When I get time I will recompile joe with the proper directory heirarchy, unless someone else does it first.

tc/rc.d/rc.sysinit.author has been modified to set the IP address. This interferes with version 4.0.1's ability to set the IP address using DHCP. I suggest that for version 4.0.1 (possible 4.0?) the calls to "ifconfig" and "route add" are unnecessary and should be removed.

Great suggestion! Specifically which versions have the dhcp client?

[Buckeyes1995]

Actually, I think it may have been due to not having my USB ethernet plugged in.. I hooked up ethernet, booted it up and everything is ok now.. not sure what was going on.

Thanks,

Jim

Originally posted by NutKase
One of you post your output from the serial session (hopefully in a .txt attachment :)) We need more info.

NutKase

[Sleeper]

Originally posted by NutKase
You may have to rememver to 'disable' the netfilters entries in rc.sysint however.

That is taken care of when you choose SA at the networking question.

[Sleeper]

Originally posted by Andy in NYC
As you know by now, I have a HDVR3 with .b running. What part(s) of TivoWeb don't work - it seems to be running just fine after my cursory testing.[b]

Tivoweb does not work on 4.x units. 3.x units are fine!

[b]Since my Tivo still seems to search for a dial tone after I make the ,#401 pre-fix, how will it 'call home' if I order pay per view, etc.? Is this failure by design, or am I missing something. The error is 'no dial tone'.

There seems to be some debate as to wether the HDVR2 can actually make its daily call via the internet. A few have claimed that they have it working. Others have gone to great lenght and can not get it working. Fixsub prevents the daily call. What reason would you want to make the daily call anyway?

I believe that pay per view calls the direct TV number and not the Tivo ISP numbers, So ppv's will need a phone line. This is just my thinking and is UNCONFIRMED. If someone knows differently, please comment.

[Sleeper]

Originally posted by Buckeyes1995
The script is quite impressive, but I have the same problem.. in Hyperterm I can see the bootup, but can't actually get a bash prompt. Any ideas?

Yes, BASH is started in the rc.sysinit.author script. If you can telnet to your Tivo and get a prompt then BASH is running.

Test your serial cable by shorting the outer 2 pins together and typing on your terminal. Characters should be echoed to your terminal. Make sure flow control is disabled in your terminal.

[Sleeper]

Originally posted by NutKase
It appears by the log that you're booting the 3.0 kernel then monte'ing successfully into... ...the 3.0 kernel again.?.


The 3.1U5, the 3.1.0 and the 3.1.1b versions all run the 3.0-Tivo-2.4.4 kernel. You are seeing the kernel version, not the software version.

Remember, the only difference between these kernel versions is the initrd. The actual kernel is the SAME!

The boot process does not printout the software version.

[Sleeper]

Originally posted by creepy
I did notice a glitch when the script says that it is appending to the .author file during the last phase of the install, it said that it is is adding "#Waiting for sat data" or something similiar. That never gets appended to the file. Doesn't affect anything, but just thought I'd bring it up in case you wanted to fix that.

Thanks again Sleeper for all you efforts!!!!!

Your Welcome.

...and you win prize for actually reading what's going on and verifying it. You are correct and that has been noted and corrected. Thank you!

[NutKase]

Originally posted by Sleeper
The 3.1U5, the 3.1.0 and the 3.1.1b versions all run the 3.0-Tivo-2.4.4 kernel. You are seeing the kernel version, not the software version.

Remember, the only difference between these kernel versions is the initrd. The actual kernel is the SAME!

The boot process does not printout the software version.

Well, the problem is that I have no idea what versions that everyone is monte'ing into with your scripts... I thought that he was monte'ing into a newer kernel.

Monte'ing from a 3.x to a 4.x system should give you a;
Linux version 2.4.18 (build@buildmaster19) (gcc version 3.0) #33 Tue Aug 5 19:51:28 or something similar kernel entry when you get a successfull monte into the 'new' software version.

Maybe I'll just let you handle it since I don't even have your scripts available to look at... (I can't burn your .iso right now due to a firmware prob w/my DRU510.)

Can you email me the scripts just so I can get a little smarter on your .iso without needing to run it?

NutKase

[BioHazard]

Hi I used your ISO, and I think it's great, i have had tried to monte my unit all day long but with your ISO it took me 20 min, but I have a problem, i can't edit the rc.sysinit.author file, because it says its a "read-only file system", I've tried chmod it 777 via the hyperterminal and a ftp client(smartftp) but i can't, neither can I overwrite the file, and I think that this happens with all the files

1.) What model is your unit?
HDVR2

2.) How big is the original hard drive?
40 GB

3.) Is or has your original hard drive been hacked before.
NO

4.) Have you ever performed a mfsrestore to your original hard drive?
YES

5.) What version of software is running on your original hard drive?

3.1.0-01-2-151

6. ) Has your box been subbed, receiving DVR service and DTV if it's a DTivo?

NO

7.) What size is the drive that your are restoring to?

120 GB

8.) Were there any error messages when running the scripts and exactly what did they say. If you are not sure then perform the entire operation again before posting.

There were no errors

9.) Include the text captured from your terminal (hyperterminal) where the error occurred in your post.

tivo:/var/tmp$ chmod -R 777 /etc/rc.d/rc.sysinit.author
chmod: /etc/rc.d/rc.sysinit.author: Read-only file system

10.) Did you spill coffee on your Tivo while you had it open? Just kidding?

Just a little

11.) Did you test the drive in your tivo after the RESTORE phase and before the SURGERY phase? Did it work?

YES

12.) Did you test the drive in your tivo after the SURGERY phase and before the FINAL (HACKS) phase? Did it work?

I didn't test it but Tivoweb, ftp, and bash seem to be working correctly except for the "read-only file system" problem.

Thanks for your help!

BioHazard

[relay]

Biohazard: You have to remount the filesystem in order to get change permissions.
type mount -o remount,rw /

[relay]

Sleeper: Is there a way to stop the scripts BEFORE it clears the boot screen information??? Now that I have a pair of 120's working I want to go back and see if I can get my pair of 160GB Seagate drives working. I would like to see what the boot screen is showing for my drives, whether they appear at 137GB drives or 160GB drives.

Thanks.....

[dogbreath]

If you really want your HDVR2 to call out via ethernet, search for "debug board" and it should answer your question.

dogbreath

[thermal]

Whoooohooo!!!

I am running a SA2 4.01 and all is working now (bash,telnet,ftp,tytools,etc)! Just a few things that didn't quite work right with the 1.01 ISO "out-of-the-box"

1. Need to patch tivoapp in order to view "unscrambled" recordings - go here to get NutKase's solution:

http://www.dealdatabase.com/forum/showthread.php?s=&threadid=25743&perpage=15&highlight=printf&pagenumber=13

2. The binary for tyserver on the ISO does not work - get a tivo superblock error. Go here to download MuscleNerds's tyserver_mfs with 4.0 compatability:

http://www.dealdatabase.com/forum/attachment.php?s=&postid=115317

ftp MuscleNerds's tyserver_mfs to your newly hacked tivo and replace the tytools in /usr/tytools. You will need to remount the root filesystem with the following command in order write to the filesystem:

mount -o remount,rw /

All is good!

[TiVoByte]

IMHO this is one of the most usefull threads on the board, has anyone considered making it stickey?

Thanks

Robert

[hickory]

Hey guys, I'm really sorry if I should have posted this somewhere else but since I'm trying to use Sleepers ISO I thot here would be a good place.

I am trying to run his CD and everything goes well except it finds my cdrom as hdd and not hdb. I have the CD drive set as Primary Slave and the Tivo drive as Secondary Master and the Fat32 Drive is set as Primary Master. I tried switching the CD drive and the Tivo but I get the same results. Basically I get the Primary showing as hda and the Tivo drive showing as hdc and the CD drive showing as hdd. Is there something easy here I'm missing? The welcome screen talks about passing extra parameters to the kernel but trying that hasn't worked either. This is the same pc I used to extreme my DSR6000 without a hitch.

[Sleeper]

Originally posted by hickory
Basically I get the Primary showing as hda and the Tivo drive showing as hdc and the CD drive showing as hdd. Is there something easy here I'm missing?

hda = Primary Master - FIRST CABLE
hdb = Primary Slave - FIRST CABLE

hdc = Secondary Master - SECOND CABLE

Move CD from second cable to first cable!

[hickory]

Thanks Sleeper, I appreciate your responding.

[midnightmaraude]

So my windows HD is NTfs. Would this iso work if i create a partition on it and format it as fat32? Or does this iso only call from hda1 whcih would be my ntfs partition. I'm trying to figure out how to get this file to restore onto my new 120gig which is fat32 formatted. Of course my option could be to get another small drive and format that fat32 but was wondering if there was anything i could do to speed hte process.. TIA

[digitaloutlaw]

Originally posted by Sleeper


Yes, BASH is started in the rc.sysinit.author script. If you can telnet to your Tivo and get a prompt then BASH is running.

Test your serial cable by shorting the outer 2 pins together and typing on your terminal. Characters should be echoed to your terminal. Make sure flow control is disabled in your terminal.

Finally! I rebuilt my cable - still no go.. then I tried another 1/8th jack and Bingo! bash prompt! The cable I bought must be off a bit somehow.. so I used an old PC speaker cable and a db9 head.. should have done this in the first place.. would have cost me like 25cents..

THanks for your help Sleeper!!

[Sleeper]

Originally posted by midnightmaraude
So my windows HD is NTfs. Would this iso work if i create a partition on it and format it as fat32

No.

You need a FAT32 drive. It doesn't have to be that big. Most images are 300 to 400 meg without recordings. Surely, you must have an old drive around.

[relay]

If this post does not belong here please move. I posted here since I used this image to setup my system.

Any one care to help me diagnose a problem with the FTP server? It was working until I brought the unit home.
Web access works perfectly.
I commented out the FTP commands from rc.sysinit.author and started it manually. It loaded without any errors but I get no response from the Tivo.
I had tried the basic FTP using IE 6 and it froze. Left for awhile and came back and there was a listing of the root. Could no go any deeper though. I check my net parms. and they seem OK.
Since I don't get any errors to check out I am at a loss...

[defaults]

I just used the script and everything is working. Great script but my only question is how can i edit the rc.sysinit.author and the rc.sysinit. I tried vi, joe and ftp but it keeps saying its a Read-only file system. Is there a command to change it so I can edit or replace those 2 files? I also tried chmod 777 /etc/rc.d/* which didn't work. any suggestions?

[digitaloutlaw]

Originally posted by defaults
I just used the script and everything is working. Great script but my only question is how can i edit the rc.sysinit.author and the rc.sysinit. I tried vi, joe and ftp but it keeps saying its a Read-only file system. Is there a command to change it so I can edit or replace those 2 files? I also tried chmod 777 /etc/rc.d/* which didn't work. any suggestions?

you need to mount -o remount,rw / to be able to edit the files.

DO..

[Andy in NYC]

I'm not the linux god around here (more like the horse stall cleaner), but I remember that you are also supposed to umount (unmount) after you are through with your changes - otherwise either BTH (bad things happen) or your Tivo has to do something on its own which slows down the boot process. This is al