Upgrading Your Hacked HR10-250 to 6.3

[kimsan]

I followed a thread at the other site. I believe it was the MovieLoader meets HMO/HME, or sumthing of the such. What an app !!

Hadn't looked into that yet. Does it require the hmo/hme patches? I've only got 30 sec, backdoors and noscramble in place just now.

In a nutshell, I dloaded the the mfs_ftp files, and the mfs_utils, I never found the s2bins file Steve mentions. When you get the utils, grab the no.arch file too, it is in the same post. It has the 2 patches in it. That took me forever to find.

The only other thing I remember is that you need a tzoffset.txt file, and I did a manual edit that Steve mentions to the mfs_ftp.tcl file. My edit was at a different line number than his.

I'd say I've done all that, but I'll just start from scratch and see what happens. s2bins were superceded but the unified mfs_utils a while back.

Thanks for the tips.

[addicted4life]

The HMO/HME is all part of what they have posted at the Playground for the hr10-250.
Go back in this thread and read over what I posted about getting from 3.1.5f to 6.3 with a pre-zippered drive. It took me a few tries to get it to work correctly.

[kimsan]

The HMO/HME is all part of what they have posted at the Playground for the hr10-250.
Go back in this thread and read over what I posted about getting from 3.1.5f to 6.3 with a pre-zippered drive. It took me a few tries to get it to work correctly.

Hadn't looked deeply into it as yet. Movieloader looks very nice and found the link there to the setup reference. Looks good on the "pull", no to try a "push" :)

Been through (and still worling on) a straight from zippered 3.1.5.f to 6.3b on the primary system. Tried to get a backup first but abandoned hope after 28 hours. mfsbackup is mighty slow on a pair of loaded 250gb drives. Will take the plunge later today.

Thanks for the nudge in the right direction!

[SteveTrek]

It's fixed now. I tried to upload a new version of the enhancement script earlier today and it kept getting corrupted during the FTP transfer. Seems to be working now.

HI,

Where can I download this fix? I tried the link below your message: Hack your Tivo with The Zipper. This contains the bad rbautch_files.tgz.

Thanks.

[kimsan]

The HMO/HME is all part of what they have posted at the Playground for the hr10-250.
Go back in this thread and read over what I posted about getting from 3.1.5f to 6.3 with a pre-zippered drive. It took me a few tries to get it to work correctly.

Got it now! My issue was in all the changes required for 6.x to run it.

Followed the basic instructions linked in the Movieloader thread to install, patch. and upgrade binaries.

Symlinked improt to stdimport.

Kept the original tzoffset.tcl, but created a tzoffset.txt with the correct GMT offset.

Runs like a champ! And Movieloader is definitely sweet.

Oh yeah, I saved off my patched files and offset so any subsequent rebuild takes only two steps :)

Thanks for the kick in the right direction.

[rbautch]

HI,

Where can I download this fix? I tried the link below your message: Hack your Tivo with The Zipper. This contains the bad rbautch_files.tgz.

Thanks.I meant that I fixed it on the zipper website.

[Cure]

I've had pretty good luck so far: reimaged with IC, Zipped and tweaked and then sliced up to 6.3a and never lost networking. However, I miss Russ's splash screen and TivoWebPlus doesn't seem to work (and I couldn't find it). I installed it to var/hack like they say but I have to start it manually via telnet. I have no clue how to edit my rc.sysedit.author file to make TWP start automatically.

Any reason not to just rerun tweak? And if so, do you have to run the tweak uninstall first?

Thanks to everyone for all their hard work.

[SteveTrek]

I meant that I fixed it on the zipper website.

I finally got by the "unexpected end of file" errors when zipper tries to open rbautch_files.tgz but it was painfull. I had to copy the file directly to the /hacks directory and delete the one that zipper copies from the CD ISO image.

As was stated by someone else (forgot who but that thanks for the info), the act of placing this file into the ISO image corrupts the tgz file! I tried MagicISO as was suggested and removed the old one and placed a good one back into the ISO file but upon re-running zipper, same old problem. I guess all that zipper does during installation is test the integrity of the tgz file. Is this correct? When I later ran tweak.sh, it tried to download it again, failed but claimed my network connections were OK. I tried several times but the script kept exiting. I finally got by this problem by insuring I ran tweak.sh from the /hacks directory by cd ing to it first! If you try running it from /var/tmp with /hacks/tweak.sh, it will never run!

Now I got all the enhancements installed (I think). I still ran into one issue:
While installing the enhancements, I got the following prompt:
Do you want to install the gotomydvr remote access tool? [y/n]:
: No such file or directoryh

Enhancement Installation Complete!! Please reboot now...

Was there something else to install beyond gotomydvr or is the script really complete?

In the description of TWP 1.3.1, its shows an MRV module. After all this upgrading, mine does not have this. How to I obtain it?

Thanks.

[sk33t3r]

I was snooping around on DDB and found that somone has put up the 6.3b slices in rar format, I have them up here (http://www.jeanandrick.com/tivofiles)

[rbautch]

I was snooping around on DDB and found that somone has put up the 6.3b slices (http://www.************.com/forum/showpost.php?p=272516&postcount=942) in rar format
Can't post links to DDB on this site.

[rbautch]

I finally got by the "unexpected end of file" errors when zipper tries to open rbautch_files.tgz but it was painfull. I had to copy the file directly to the /hacks directory and delete the one that zipper copies from the CD ISO image.

As was stated by someone else (forgot who but that thanks for the info), the act of placing this file into the ISO image corrupts the tgz file! I tried MagicISO as was suggested and removed the old one and placed a good one back into the ISO file but upon re-running zipper, same old problem. I guess all that zipper does during installation is test the integrity of the tgz file. Is this correct? When I later ran tweak.sh, it tried to download it again, failed but claimed my network connections were OK. I tried several times but the script kept exiting. I finally got by this problem by insuring I ran tweak.sh from the /hacks directory by cd ing to it first! If you try running it from /var/tmp with /hacks/tweak.sh, it will never run!

Now I got all the enhancements installed (I think). I still ran into one issue:
While installing the enhancements, I got the following prompt:
Do you want to install the gotomydvr remote access tool? [y/n]:
: No such file or directoryh

Enhancement Installation Complete!! Please reboot now...

Was there something else to install beyond gotomydvr or is the script really complete?

In the description of TWP 1.3.1, its shows an MRV module. After all this upgrading, mine does not have this. How to I obtain it?

Thanks.
I'm having problems with the gotomydvr stuff. I'm just going to remove it for now. It's easy enough to install it yourself anyway. Not sure what the issue with the tgz file is. The isomaker copies it on to your boot iso, and the zipper copies it to your tivo. That's it. One possibility is that the limitation of the isomake is 300MB, and if you go over that it may be truncating/corrupting the file. Seems to work fine for me.

[sk33t3r]

What are the commands to use dbload to load slices into mfs?

[guido79]

What are the commands to use dbload to load slices into mfs?

After putting my slice files into /var/packages/ on my Tivo, I typed: dbload *.slice

After all 5 files were loaded by dbload, I typed: echo mls /SwSystem | tivosh

Now I show the following:

Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
3.1.5f-01-2-357 tyDb 3180 09/29/06 23:56 700
6.3b-01-2-357 tyDb 193180 01/02/07 07:51 772
ACTIVE tyDb 3180 09/29/06 23:56 700

[Lord Vader]

I was snooping around on DDB and found that somone has put up the 6.3b slices in rar format, I have them up here (http://www.jeanandrick.com/tivofiles)

I'm assuming one need only ftp the rar'd file in its entirety, correct? Or should it be extracted then the extracted contents ftp'd over?

[guido79]

I'm assuming one need only ftp the rar'd file in its entirety, correct? Or should it be extracted then the extracted contents ftp'd over?
Nope. You'll want to unrar first, then ftp over the .slice files to /var/packages/. I just upgraded successfully using The Slicer - Version 1.4. Everything looks to be working fine (i.e. Networking, Telnet, FTP, etc.).

[DarthOverlord]

I was snooping around on DDB and found that somone has put up the 6.3b slices in rar format, I have them up here (http://www.jeanandrick.com/tivofiles)

Thanks. I have been trying to download it from the stream for the past four days without any luck.

[mrsean]

Just wanted to mention that I too am experiencing the corrupted "rbautch_files.tgz" problem. I am assuming that I could just FTP it over to the TIVO, but which directory do I unzip the file into?

Thanks!


I'm having problems with the gotomydvr stuff. I'm just going to remove it for now. It's easy enough to install it yourself anyway. Not sure what the issue with the tgz file is. The isomaker copies it on to your boot iso, and the zipper copies it to your tivo. That's it. One possibility is that the limitation of the isomake is 300MB, and if you go over that it may be truncating/corrupting the file. Seems to work fine for me.

[Lord Vader]

Nope. You'll want to unrar first, then ftp over the .slice files to /var/packages/. I just upgraded successfully using The Slicer - Version 1.4. Everything looks to be working fine (i.e. Networking, Telnet, FTP, etc.).

I must admit, I don't know if I'm going to attempt to upgrade. The last time I did it, everything went to pot. I lost ALL connectivity, including serial, and lost all hacks. I had to end up re-imaging from 3.1.5f to 6.3a, where I'm at now. The perplexing thing was that I did nothing different from when I used Slicer to upgrade from 3.1.5f to 6.3a. That went fine. Why going to 6.3b, though, caused so many problems still baffles me.

[Cure]

Lord Vader -

Did you slice directly from 6.3a to 6.3b? Or did you go back to 3.1.5 first?

[sk33t3r]

I have the slices on my machine from dtv, but I thought it be nice to make them available. I put a 62 dtivo image up as well. Tivo Files (http://www.jeanandrick.com/tivofiles)

[Lord Vader]

Lord Vader -

Did you slice directly from 6.3a to 6.3b? Or did you go back to 3.1.5 first?

I went from 6.3a to 6.3b, just like so many others here did. Unlike them, however, my upgrade didn't go well. At all.

[guido79]

I seem to be still running fine since the Slicer upgrade using the downloaded 6.3b slices. Here's what I did to get to where I am today:

- I started with a brand new 500 GB Seagate drive [ST3500841A] from Fry's.
- I setup my new drive with the Zipper CD following the instructions on D*Rplayground.
- I opted to buy InstantCake 3.1.5f for the HR10-250, DVRupgrade LBA48 4.04 w/ Enhancements CD and The Slicer to make my Zipper CD.
- Created my Zippered Tivo Hard Disk after fixing the instructions to run:
/cdrom/zipper instead of sh /cdrom/zipper.sh
- Installed and ran the Zippered drive in my Tivo for a week after modifying the phone settings to use the network connection (using a Linksys USB200M adapter) for service calls. [Hoping to download the 6.3b slices naturally].
- After the holidays, I gave up and installed the 6.3b slices myself via FTP after unraring the archive.
- Everything seemed to be running OK except for TivoWebPlus. I reran the tweak.sh script located in my /hacks directory and now everything seems to be running fine.
- I've updated my TivoWebPlus to the beta 1.4.0 via TivoWebPlus's upgrade page.

Hope this helps those who have been struggling.

[gworkman]

Wow! I've got my own success story. Downloaded and installed the 6.3b patch. Sliced and patched and everything is working. I even have the HMO/HME feature which was one of the biggest incentives for me to make it work. I had to zipper the drive twice in the PC. The first time, I'd get responses like "IP : Command not found" on the first run. The second run gave me telnet/ftp/twp. I then added the hacks to enable HMO. I see that the welcome screen even talks about the box being more than a "DirecTV recorder". What a shame that all this code is in there and DirecTV decided to go with the HR 20 instead. I am 100% satisfied with my HR10-250. RBautch and all other hackers that made this possible ... THANKS !!!!

[tsunami]

I am having a couple of problems with my HR10-250 with 6.3b zippered and enhanced.
First problem was when I would search for a program I would get an internal error code. I reset the TiVO and it worked fine.
Now when I search for a program it doesn't seem to find much of what I want.
For example, tonight Knights of Prosperity is in the guide but if I search for it it doesn't show up.
I wonder if it could be from scheduling/deleting shows with TWP? I haven't used it to rearrange the Season Pass. I have set programs to record, wishlist, etc.
Could that be it?
It is also running a little hot (58C).
Any ideas?
I guess a reset will do it but I would like to know how to keep it from happening again.

[Brillian1080p]

sk33t3r, Just thought you should know when you follow your link to tivo files and click on the HR10-250, it does not open up a box to save the file like the other versions. It just opens up text.

The HR10-250 is the one I'm interested in, and I'm sure others will be also.

[DarthOverlord]

OK, here is my question. Yesterday I ftp'd the 6.3b slices onto my HR10-250. So when I check the mfs file it lists both the current and 6.3b system files. Now, if I reboot my machine, will the 6.3b files overwrite my zippered drive? The reason I ask, is there a away to remove the 6.3b system file and keep the 3.15f as is. I am afraid if I pull the drive now, it will install 6.3b on this drive, when I want to keep it at 3.15.

After this, I want to restore my vigin 3.15f image onto another drive, then upload the slices, upgrade and then rezipper that drive. I would keep the original drive, in case I wanted to go back to 3.15.

Can I remove 6.3 off the current HR10 drive? Thanks.

[gregoryb]

Upgraded my HR10-250 to 6.3b using Slicer. All working well after running tweak. Problem is with MRV. My other Tivo and Tivoserver shows up but when I select them it shows a copy of my Now Showing list. I have rechecked all network settings and MRV Name in TWP and all looks good. Any suggestions?

[guido79]

Problem is with MRV. I have rechecked all network settings and MRV Name in TWP and all looks good. Any suggestions?
HMO works with HR10-250 but no support for MRV even with hacks.

[DarthOverlord]

Can anyone answer how to prevent 6.3 from installing if I reboot the HR10-250?

Since the bootpage parameter upgradesoftware=false, I assume this would prevent any upgrade from occurring, is this a correct assumption?

[sk33t3r]

Can anyone answer how to prevent 6.3 from installing if I reboot the HR10-250?

Since the bootpage parameter upgradesoftware=false, I assume this would prevent any upgrade from occurring, is this a correct assumption?

You are correct, it will download the slices but will NOT install them, you can check via tivoweb if the slices are downloaded, http://ipaddressoftivo/mfs/SwSystem

[DarthOverlord]

You are correct, it will download the slices but will NOT install them, you can check via tivoweb if the slices are downloaded, http://ipaddressoftivo/mfs/SwSystem

Thanks. That's what I needed to know.

[Brillian1080p]

Is dbload part of the tivoapp or is an additional script that needs to be downloaded? I noticed on that other site that AW has all in one tools and I believe dbload is part of it, but editing the author file is required and I'm not that far yet.

[sk33t3r]

Its in /busybox

[Brillian1080p]

Well I have the 6.3b slices from another site. tried dbload from the command prompt. It took a minute, seemed to be working and came back to the bash. I looked in thw sw system and they are not there.

Does the root need to mounted read/write?

I rebooted to see if they would show up and it wiped them from var/packages.

Any info/commands/keystrokes you're leaving out?

I'm close...

[Brillian1080p]

Should it matter that I have 3.1.5f active and 6.3a sitting there?

I know if I slice from 3.1 to 6.3a it will wipe out the 3.1 in a day or so. I believe I've seen someone have 3.1 6.3a and 6.3b sitting in there. I've tried dbload 3 times now with no success.

[sk33t3r]

OS has to be RW

I just downloaded the rar file and it worked fine here.

I created a tarball of the slices, that way all you have to download the tarball, ftp the tarball to the hr10-250 and then telnet to the tivo and extract the tarball using tar-xf hr10_250_6.3bslices.tar

[Brillian1080p]

I have them, it was Firefox that wouldn't let me download them. Why it would allow the other versions you have on the site I don't know.

I can't seem to get dbload to work.

[DarthOverlord]

OK, here is my scenario. Took my original Zippered drive out of the HR10-250. Restored my 3.15f image to another 250 GB Seagate with the Zipper. FTP'd the 6.3b slices over, dbsliced them.

Then I changed etc/rc.d/sysinit.author to remove the netmask settings as mentioned by rbautch on the first page. I checked the partition location via 'bootpage -p". Subsequently, I changed the bootpage setting to remove the softwareupgrade=false setting.

I then rebooted the system. My understanding is that the upgrade should have taken. Yet when I rebooted, I am now running unhacked 3.15. Where did I go wrong?

My goal is to upgrade to an unhacked 6.3b, test it for a few hours, then pull the drive and rerun the zipper.

[Brillian1080p]

You cannot hack straight from 6.3. You have to start with 3.1, hack that, upgrade to 6.3 then you can run the enhancement script.

Rbautch has said zippering 6.3 will be available when he gets an image of it.

Paraphrasing , of course.

[DarthOverlord]

You cannot hack straight from 6.3. You have to start with 3.1, hack that, upgrade to 6.3 then you can run the enhancement script.

Rbautch has said zippering 6.3 will be available when he gets an image of it.

Paraphrasing , of course.

Oh, I see said the blind man. So right now, I am SOL, if I want to upgrade to 6.3b zippered.

I have been trying to get the network settings to stick after the initial zipper on the hard drive and have been getting etc/resolv.conf not found.

Oh well. Thanks.

[MidnightRider]

Hello all: here's a question I haven't found an answer for here or on the "other" forum:

I have a HR10-250 that I had previously hacked with the Zipper. I've also expanded to use a 2nd hard drive.

I used the Slicer to upgrade to 6.3a, then (when it showed up on my tivo) 6.3b. During the 6.3b process, something happened ... upon reboot (and subsequent reboots) although I have network connectivity (can see network lights, ping and get response from the tivo) I have no TWP, telnet or serial access (serial says connected but no bash prompt ... at any speed). For all intents and purposes other than 'ping', it's like I've never hacked the thing.

My question is this: when I pull the drive(s) and re-zipper, do I need to install both drives in the pc or can I just install and zipper the "main" (primary) drive? Put another way, are there any special considerations I need to make since I'm using two drives?

[Lord Vader]

Welcome to the club, Midnight. I lost all connectivity too, for some unknown reason.

[MidnightRider]

Thanks, I guess. Zippering is easy enough; I'm just not enough of a Linux junkie to know if I need to do anything special since I've expanded to two drives.

MR

[Brillian1080p]

Darthoverlord, after reading your post again I think I understand it better.

1. After you used dbload to move the 6.3b slices into the SwSystem did you use the slicer to upgrade it? You post doesn't mention that.

2. Without hacking you will have to use a serial cable to use the slicer to upgrade from 3.1 to 6.3. If you want to test 6.3b unhacked you can, but once you are satisfied you will have to re-image 3.1 and slice upgrade to 6.3.

Since you have successfully used dbload please give specifics.

1. Do you mount it read/write?

2. Do you navigate to the directory where dbload is located? Such as /busybox.

3. What does the bash report while executing dbload?

I've tired # 1 and # 2 with no success. The slices ftp over fine. I put them in /var/packages. I type "dbload *.slice". The bash comes back with dbload: *.slice, the cursor flickers for a minute then bash comes back. But the slices never show up in the SwSytem.

If the command was incorrect or the box didn't know what to do with it you'd think an error message would come up.

[Brillian1080p]

Lord Vader, I've sliced a few times from 3.1 to 6.3a and retained connectivity. I had 6.3a running perfect. I used MFS tools to make a backup and munged it up. I may have forgotten to change it from rw to ro.

Today however every time I get to 6.3a I lose connectivity. Both FA120 lights are on, no ping no serial. Now I'm in the same boat.

Something has changed. Not sure if it can be blamed on the script because 3.1 works fine after running tweak.sh.

[DarthOverlord]

Darthoverlord, after reading your post again I think I understand it better.

1. After you used dbload to move the 6.3b slices into the SwSystem did you use the slicer to upgrade it? You post doen't mention that.

2. Without hacking you will have to use a serial cable to use the slicer to upgrade from 3.1 to 6.3. If you want to test 6.3b unhacked you can, but once you are satisfied you will have to re-image 3.1 and slice upgrade to 6.3.

Since you have successfully used dbload please give specifics.

1. Do you mount it read/write?

2. Do you navigate to the directory where dbload is located? Such as /busybox.

3. What does the bash report while executing dbload?

I've tired # 1 and # 2 with no success. The slices ftp over fine. I put them in /var/packages. I type "dbload *.slice". The bash comes back with dbload: *.slice, the cursor flickers for a minute then bash comes back. But the slices never show up in the SwSytem.

If the command was incorrect or the box didn't know what to do with it you'd think an error message would come up.

Give me a minute to write up the recipe.

[Lord Vader]

Lord Vader, I've sliced a few times from 3.1 to 6.3a and retained connectivity. I had 6.3a running perfect. I used MFS tools to make a backup and munged it up. I may have forgotten to change it from rw to ro.

Today however every time I get to 6.3a I lose connectivity. Both FA120 lights are on, no ping no serial. Now I'm in the same boat.

Something has changed. Not sure if it can be blamed on the script because 3.1 works fine after running tweak.sh.

I had no problems with my connectivity when going from 3.1.5f to 6.3a. My problems arose whenever I attempted to go from 6.3a to 6.3b.

[Brillian1080p]

I don't even use ota right now. If the only difference between 6.3a and b is the fix for ota audio dropouts, then I'm trying to upgrade to b for no reason.

[DarthOverlord]

Upgrading 3.15f To 6.3b Without Using The Slicer And With Some Hacks To Start.

Step 1 – Took a blank 250 GB Seagate Drive and ran the Zipper to restore the 3.15f image I made from my original HR10-250 drive.

Step 2 – Ran the Zipper to apply the hacked kernel and set up networking. Reinstalled drive into HR10-250. It ran through the setup, reboot partially into satellite scan, then went through the normal startup process.

Step 3 – Telnet into Tivo. Use SmartFTP to install slices obtained here - http://www.jeanandrick.com/tivofiles. Thanks sk33t3r. Upload slices to var/packages
Go into telnet. Run
mount -o remount,rw /dev/hdax

(where x is either 7 or 4), use the command
bootpage –p
to figure it out which is the active partition.

Step 4 – Make sure you are in the /var/packages directory and enter
dbload *.slice

Now wait about ten minutes for the slices to be put together. Then enter:
echo mls /SwSystem | tivosh

I then followed rbautch’s recommendations:

Well, it's official. Those of us with HR10-250's running painfully slow 3.1 software will finally get the upgrade to 6.3. The new release is being discussed here (http://www.tivocommunity.com/tivo-vb/showthread.php?t=315176) (thanks, Earl!). If you have a hacked HR10-250, and want to keep it hacked, here are a few options for you.

Option 1. Take the upgrade, let it overwrite your hacks, and then re-hack it at a later time. There's two things you need to do in preparation for the upgrade. The first is to edit your author file to remove the following lines: route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0 Then type the following command at the bash prompt to modify your bootpage to allow the upgrade: bootpage -P "root=/dev/hdaX dsscon=true console=2,115200" /dev/hda where X is your root filesystem partition (either 4 or 7). Make sure you get this right or your Tivo won’t boot. After you get the upgrade, pull the drive and hack it.

This next part I have to give credit to kehrli from DVR ground where you play.

• Edit /tvbin/installSw.itcl and find
exec /var/utils/updateroot /dev/hda /install /var/packages >&@ stdout
change it to
exec /var/utils/updateroot /dev/hda /install /var/packages $name >&@ stdout
A few lines further down, find reboot
change that to exit 0
The first change is needed or the script will not run to completion. The 2nd change prevents the reboot from occurring so we can install our hacks in the new root artition.
• Run bootpage -p. This will give you where your current root partition is located. It should be either /dev/hda7 or /dev/hda4. TiVo uses two pairs of partitions for loading its software. One pair is active with the current software version. Then if you upgrade your software, it'll get loaded to the other pair, and then that pair becomes active. The bootpage command will tell you which drive partition is being used for the TiVo's file system root. If you then run bootpage -b it will tell you the current boot partition (the partition where your Linux kernel lives). The pairs are set up as one of the following: root=/dev/hda7 boot=/dev/hda6 OR root=/dev/hda4 boot=/dev/hda3. Write down the results from the bootpage command. You MUST know your root and boot partitions prior to proceeding. You must not get these wrong. Some rare bootpage documentation is supplied at the bottom of this document.
• Run installSw.itcl 6.3b-01-2-357. This should run to completion and not leave you with error messages, telling you which files and line numbers had the errors. If you get errors, one of the earlier steps is wrong and you'll need to find and fix it. Not well: the software version number in the command above may be slightly different. Get the exact string to enter by using echo mls /SwSystem | tivosh

This last part also took about ten minutes. I then proceeded to reboot my HR10-250, since I was not trying to keep any hacks.

The HR10-250, went through a semi-long update about 15 minutes or so. Viola, I now had an update system with 6.3b running. Beautiful folders, ahhhh!!!!

Step 5 – Replacing the virgin 6.3b kernel with the hacked kernel.

I basically took the drive out and ran the zipper again. The only problem was that I was getting this message:

The file /tivo /etc/resolv.conf is missing
The file /cdrom /etc/resolv.conf is missing

So when I tried the drive in the Tivo, I could not for the life of me get into the bash prompt or telnet in. I then was given this advice by dswallow:

DarthOverlord, I did an upgrade from an unhacked 6.3b HR10-250 so I can probably be of some help here.

I'll presume you already have installed the hacked/killhdinitrd'd kernel from 3.1.5f on the $5 PTVUpgrade CD onto the HR10-250.

There's two main issues to deal with. One is that the network configuration settings are stored in the mfs filesystem. There's two scripts you can choose from... /hacks/network.tcl from RBautch or netconfig.tcl (see the SuperPatch/MRV thread over in the "other" forum). If you look at them with a text editor you'll see the command line parameter info.

In your /etc/rc.d/rc.sysinit.author file you need to comment out the insmod entries for the older USB drivers, the entries for the USB disk devices, and the ifconfig and route lines for configuring the ethernet interface the old way.

Leave the "sleep 60" command in there, but the 2 earlier ones can be commented out, too.

Replace that with a call to one of the scripts above and the necessary parameters for your setup. Also note at the end of the rc.sysinit.author file will be a call to network.tcl inside a couple if blocks; that'll essentially be what you want to run earlier too... just the line with network.tcl on it, so you could just duplicate that line (it'd have been populated based on your answers to prompts from the enhancement script).

Then you need to replace the iptables file with one that doesn't block network traffic:

cd /sbin
mv iptables iptables.old
echo -e '#!/bin/bash\nexit 0' > iptables
chmod 755 iptables

Now place the drive back in the TiVo and boot it up; the first time through the network settings will get loaded into the filesystem, but your network won't be working yet since they hadn't been set early enough; you need to reboot once more. Restart the TiVo and the second time the network settings will take effect. You can then telnet in and edit the rc.sysinit.author file and remove the call to the network setting script.


BTW, 6.3b has the network settings pages; if you have applied the 3 patches for the HMO/HME services, you'll find the network settings under Settings / Phone / Change Phone or Network Settings.

I'm not sure if that process will deal with the iptables file or not, though.

At this point the ftp and telnet services should work over the network, presuming they did get installed in your rc.sysinit.author file to autostart.
So I followed his directions, by putting the drive back in the computer,

I ran the following:

1. Created a mount point for the partition and mount it:
mkdir /mnt/mnt4
mount /dev/hda4 /mnt/mnt4
2. Changed to the directory that will house rc.sysyinit.author
cd /mnt/mnt4/etc/rc.d
3. Editted rc.sysinit.author:
pico rc.sysinit.author


#!/bin/bash
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10
tnlited 23 /bin/bash -login &
tivoftpd
route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0
fakecall.tcl

/bin/bash </dev/ttyS2&> /dev/ttyS2&
#insmod /lib/modules/usbcore.o
#insmod /lib/modules/ax8817x.o
sleep 60
#ifconfig eth0 192.168.0.175 netmask 255.255.255.0
#route add default gw 192.168.0.1
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /

#call network.tcl
/hacks/network.tcl 192.168.0.175 192.168.0.1
fi
fi

I then hit ctrl x and saved it. Then I edited this part:
cd /mnt/mnt4/sbin



cd /sbin
mv iptables iptables.old
echo -e '#!/bin/bash\nexit 0' > iptables
chmod 755 iptables
Then I reinserted the drive, allowed it to boot up once, then I rebooted and viola – bash prompt appeared and I am able to telnet.

The problem now is my bash prompt works, but does not respond to ‘ls’ or ‘./’ commands. I can change directories and gzip and some other things, but not some of the basic linux commands. Any help would be much appreciated.

[Brillian1080p]

Man that seems like a lot of work. I used the slicer, I think it does most of that by script.

I ftp'd the tarball over and untarred it and now dbload is working. It didn't like the slices ftp'd over individually. I don't know why?

Thanks guys.

[dswallow]

Personally I'd recommend just letting 6.3b install by itself then rehack it manually rather than depending on something like the Zipper, which apparently isn't updated yet to work directly from 6.3b. You'll keep all your recordings that way. :)

[Brillian1080p]

If you don't have 6.3b sitting in the mfs then it could be a long wait.

If you let 6.3b install itself it will wipe out any hacks which include usb/ethernet connectivity and you're back to a serial cable.

There are ways you can keep your recordings and upgrade.

31,656 posts in 6 six years, what am I telling you anything for?

Ignore everything I say for another 31,556 posts...

[Brillian1080p]

I finally waited long enough for dbload to finish. It went back to the bash prompt after it loaded the 5 files. But they still are not in the mfs even after a reboot. What step am I missing here?

Out of curiousity, what step does the box do to combine the 5 slices and rename them 6.3b-01-2-357?

Or is that the step I'm missing?

[PorkPie5000]

Hey Vader, I'm in exactly the same boat that you are. Went from 6.3a to 6.3b using slicer and lost network except for ping.

I'm curious about something though. Have you actually gone to system info and looked at what version you are actually running? Mine still says 6.3a. Something didn't happen that was supposed to happen during the upgrade. I'm not sure what though.

[Lord Vader]

I didn't check that before or after the failed upgrade. I'm now back at 6.3a and will stay there for the foreseeable future.

[sk33t3r]

I finally waited long enough for dbload to finish. It went back to the bash prompt after it loaded the 5 files. But they still are not in the mfs even after a reboot. What step am I missing here?

Out of curiousity, what step does the box do to combine the 5 slices and rename them 6.3b-01-2-357?

Or is that the step I'm missing?


Brillian from your browser if you enter http://ipaddressoftico/mfs/SwSystem you dont see 6.3B loaded?

[tivoupgrade]

Hey Vader, I'm in exactly the same boat that you are. Went from 6.3a to 6.3b using slicer and lost network except for ping.

I'm curious about something though. Have you actually gone to system info and looked at what version you are actually running? Mine still says 6.3a. Something didn't happen that was supposed to happen during the upgrade. I'm not sure what though.

If you are attempting to use slicer to get you from 6.3a to 6.3b OR even from 3.1.5f to 6.3a or b and you are using a USB 2.0 adapter (perhaps configured with PTVnet) that is why you are losing connectivity. The stock 6.3 drivers are not compatible with newer USB adapters.

Here is a post from 12/23 (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4704609&&#post4704609) which gives you a way to keep those drivers intact; actually, it doesn't keep the drivers intact - it downloads and installs updated ones which will also work with newer adapters such as the Linksys USB 2.0 adapter; note that its a pretty "big hammer" though - it will also install TiVoWebPlus 1.3 and setup the network for DHCP, too.

[Lord Vader]

Well, I AM using a NetgearFA120. In fact, as I had posted before on this problem, my FA120's lights are all on. However, I lost ALL connectivity via telnet AND serial. I did nothing differently from what others did, exept that unlike them, I lost ALL connectivity and ALL hacks.

[dswallow]

If you don't have 6.3b sitting in the mfs then it could be a long wait.

If you let 6.3b install itself it will wipe out any hacks which include usb/ethernet connectivity and you're back to a serial cable.

There are ways you can keep your recordings and upgrade.
Well, yeah, I know. But then his instructions have him removing the drive a couple times, too. If you're gonna take the drive out anyway... :)

Actually I had more in mind the idea of going from 6.3a to 6.3b as being why you'd do what he did... starting off by restoring a 3.1.5f image, since that's what the Zipper instructions suggest right now.

[tivoupgrade]

Well, I AM using a NetgearFA120. In fact, as I had posted before on this problem, my FA120's lights are all on. However, I lost ALL connectivity via telnet AND serial. I did nothing differently from what others did, exept that unlike them, I lost ALL connectivity and ALL hacks.

Actually, that makes sense; I mis-spoke. I should have said (and I'll go back and edit it now) "regardless of the USB 2.0 adapter you are using" because those drivers are not present in the stock distribution.

The part that doesn't make sense is why you would have lost all hacks - that sounds like a run that might not have completed normally. Did you lose bash access as well?

[JWThiers]

Did you lose bash access as well?
He said he lost "ALL connectivity via telnet AND serial." Thats not good.

[tivoupgrade]

He said he lost "ALL connectivity via telnet AND serial." Thats not good.

Yes. Not good. Not normal either. I have not been able to replicate anything like that.

What I can confirm is that my previous statements were somewhat misleading.

I'm trying to come up with a clearer migration path / statement that Russ can put in his original post on the thread to deal with issues of slicing from either 3.1.5f --> 6.3a , or 6.3b ---> 6.3w (w == whatever) and be able to preserve USB 2.0 drivers.

I know that a few simple commands, at the right time, should be all it takes to do this. Its possible that using the '-u' option when running the Slicer (but only when going between versions of 6.3, not from 3.1.5f to 6.3) will work because -u will copy /lib/modules from the old partition to the new.

Right now, my recommendation is to go with the 'update2' methods we've put into place and will leave alone for the foreseeable future, but its likely that when I get back from CES, I may add another parameter to that script that will allow you to just suck down the latest USB drivers.

And with all that said, I'm not sure whether that has anything to do with Lord Vader's problem, which I mistook for the simple loss of network drivers; not sure what that issue is/was, but it was definitely more complicated than that.

[dr_mal]

Looks like I finally crashed my HD Tivo, I'm hoping someone is willing to help. I've been holding off on the 6.3 upgrade until today (zippered unit). So, I purchased the Slicer program and ran the script, everything seemed like it went smoothly. The script finished without problem and I rebooted the Tivo. Now its caught in a reboot loop. I connected my serial cable and have a boot log. The last entry says:

Tmk Fatal Error: Thread convert-db <145>: unexpected signal 11
flushing ide devices: hda hdb
Restarting system.

I'm hoping I can recover without formatting and starting over. If anyone has any suggestions, I would be greatful. I can post the entire boot log if it would be helpful.

Thanks,
Aaron
Same thing happened to me just now :(

I've previously zippered this TiVo; just purchased Slicer; Slicer seemed to run fine - no errors.

Is it safe to simply switch the active root and kernel partitions and go back to 3.1f for now?

[dr_mal]

No dice - going back to the old boot and kernel partitions results in the same rebooting behaviour (albeit with my old "almost there..." screen) :(

[gobble]

Well, I AM using a NetgearFA120. In fact, as I had posted before on this problem, my FA120's lights are all on. However, I lost ALL connectivity via telnet AND serial. I did nothing differently from what others did, exept that unlike them, I lost ALL connectivity and ALL hacks.

I have the same problem. I have the FA120. All the lghts are on. I have no connectivity and lost all hacks. All this after running the slicer from 3.1.5f to 6.3a. I finally got sick of the message that the TIVO has not made a call and tried this morning to disable the automatic call. Problem is I can't network into the TIVO.

What would be the solution if I can't network back into the thing to fix anything? Restore from the backup drive and start from scratch?

[avpman]

HR10-250 hacked with zipper + InstantCake

I commented out the appropriate lines in rs.sysinit.author and was able to make a succesful daily call over the network. However, in the tclient log file I'm getting an error acquiring the 6.3b slices. Any ideas?

Jan 8 01:11:37 (none) comm[138]: checking for new software
Jan 8 01:11:37 (none) comm[138]: NewSoftware: getting SwSystem name
Jan 8 01:11:37 (none) comm[138]: NewSoftware: failure reading SwSystem 6.3b-01-2-357: errDbNotFound
Jan 8 01:11:37 (none) comm[138]: Cleanup: GetAddDiskBasedDirectories returned <70001> "0x70001"...skipping cleanup
Jan 8 01:11:37 (none) tcphonehome[138]: CallService return status 0x0

[hakamarob]

forgive me for asking short bus kind of questions, but i have had some odd issues with my hd unit since upgrading to 6.* and i want to go back to 3.1. what are my options? get an image from ptvupgrades, yank the drive and start fresh?

TIA

[aprest]

I am not sure Cron is functioning and there is no cronlog in the /var/log directory. Is there a way to see if Cron is working? Where is the log file for Cron located? I have two Tivos, one has it working and I can see the log, the other, which I hacked just after the Zipper was released for HD Tivo, is the one I can't fine the cron log for.

Should I run tweak.sh again to install cron? If so, should I run tweak-uninstall first?

I am having the same problem after upgrading from 3.1.5f to 6.3b. One of my HR10-250 STBs shows the logs and the other doesn't. Both were zippered a day apart in early December with the same CD. I think cron is working on one and the other is not. Did you find a solution?

[bigrig]

I am having the same problem after upgrading from 3.1.5f to 6.3b. One of my HR10-250 STBs shows the logs and the other doesn't. Both were zippered a day apart in early December with the same CD. I think cron is working on one and the other is not. Did you find a solution?
My reply in the other thread didn't work for you?
http://www.tivocommunity.com/tivo-vb/showthread.php?p=4748036&&#post4748036

Matt

[aprest]

My reply in the other thread didn't work for you?
http://www.tivocommunity.com/tivo-vb/showthread.php?p=4748036&&#post4748036

Matt

I tried that it it did not fix my problem. Thanks for helping.

[RxMan]

I ran slicer to get to 6.3b and had no problems except for at the very end. ctrl-c would not work for me. I don't know if it's my laptop or something else. I needed to do a ctrl-c and then run the update2 to get the drivers and tivowebplus, etc as mentioned above, but could not. Everything else worked fine. Can I run that command some other way to get the necessary files loaded and working. I have a Linksys usb200m v2 that I just connected and haven't installed tivoweb on this particular box before.

[rbautch]

I ran slicer to get to 6.3b and had no problems except for at the very end. ctrl-c would not work for me. I don't know if it's my laptop or something else. I needed to do a ctrl-c and then run the update2 to get the drivers and tivowebplus, etc as mentioned above, but could not. Everything else worked fine. Can I run that command some other way to get the necessary files loaded and working. I have a Linksys usb200m v2 that I just connected and haven't installed tivoweb on this particular box before.Try closing your telnet session and opening another. Your tivo shouldn't reboot unless you hit enter on the only telnet session.

[rbautch]

HR10-250 hacked with zipper + InstantCake

I commented out the appropriate lines in rs.sysinit.author and was able to make a succesful daily call over the network. However, in the tclient log file I'm getting an error acquiring the 6.3b slices. Any ideas?

Jan 8 01:11:37 (none) comm[138]: checking for new software
Jan 8 01:11:37 (none) comm[138]: NewSoftware: getting SwSystem name
Jan 8 01:11:37 (none) comm[138]: NewSoftware: failure reading SwSystem 6.3b-01-2-357: errDbNotFound
Jan 8 01:11:37 (none) comm[138]: Cleanup: GetAddDiskBasedDirectories returned <70001> "0x70001"...skipping cleanup
Jan 8 01:11:37 (none) tcphonehome[138]: CallService return status 0x0It's possible the slice file didn't download completely. Try forcing another call and try it again.

[rbautch]

forgive me for asking short bus kind of questions, but i have had some odd issues with my hd unit since upgrading to 6.* and i want to go back to 3.1. what are my options? get an image from ptvupgrades, yank the drive and start fresh?

TIAI think so. As far as I'm aware 3.1.5f slices aren't available.

[RxMan]

Try closing your telnet session and opening another. Your tivo shouldn't reboot unless you hit enter on the only telnet session.

It has already rebooted. What are my options now? System info is showing me at 6.3b. Just need to get the usb200m v2 and TWP going. Thanks for the quick reply. I have looked at Jamie's backported drivers, but I don't really know what I am looking at.

[Lord Vader]

Yes. Not good. Not normal either. I have not been able to replicate anything like that.

What I can confirm is that my previous statements were somewhat misleading.

I'm trying to come up with a clearer migration path / statement that Russ can put in his original post on the thread to deal with issues of slicing from either 3.1.5f --> 6.3a , or 6.3b ---> 6.3w (w == whatever) and be able to preserve USB 2.0 drivers.

I know that a few simple commands, at the right time, should be all it takes to do this. Its possible that using the '-u' option when running the Slicer (but only when going between versions of 6.3, not from 3.1.5f to 6.3) will work because -u will copy /lib/modules from the old partition to the new.

Right now, my recommendation is to go with the 'update2' methods we've put into place and will leave alone for the foreseeable future, but its likely that when I get back from CES, I may add another parameter to that script that will allow you to just suck down the latest USB drivers.

And with all that said, I'm not sure whether that has anything to do with Lord Vader's problem, which I mistook for the simple loss of network drivers; not sure what that issue is/was, but it was definitely more complicated than that.

Indeed it was. I have NO idea why I lost all connectivity, and I really don't want to try again and lose it again.

[rbautch]

It has already rebooted. What are my options now? System info is showing me at 6.3b. Just need to get the usb200m v2 and TWP going. Thanks for the quick reply. I have looked at Jamie's backported drivers, but I don't really know what I am looking at.
The drivers you need should already be on your tivo, but in the old partition. You can either mount that old partition, and copy the appropriate drivers, or download Jamie's newest drivers and install them. If you lost your connection, you have to do this either with a serial cable or by pulling the drive. Unlike 3.1.5f, where drivers are stored in /lib/modules, 6.3 stores some drivers in /lib/modules, and some in /platform/lib/modules. Some drivers have symlinks in /lib/modules that point to /platform/lib/modules. You can either keep the symlinks, or just overwrite them with the actual drivers.

[RxMan]

I still have bash via serial. I noticed Jamie had 2 different files for download. What is the difference? usbobj2.4.27 and usbsrc2.4.27
How would I overwrite the symlinks? The symlinks is the part I didn't understand. Do I move the whole tar.bz2 over or unrar it first on my computer and send over just what I need? Am I looking for something specific for the usb200mv2? Thanks again.

[RxMan]

What if I re-ran your enhancement script?

[rbautch]

That should work as long as you have the rbautch_files.tgz archive in the same directory as tweak.sh.

[RxMan]

I gave that a try. Seemed to work. Will test more tomorrow.

Thanks

[RxMan]

Well, I have lights on the usb200m, but no ip address. I ran angryIP and it didn't find anything. Also, I don't think tivoweb started bc it said something about a read only state. Not sure though. How can I tell via serial what the ip addy is?

[RxMan]

Set my router and tivo IP. I can now get connected via usb port! Need to get tivoweb going next.

[John_Hatchett]

Is there a 'zipper' receipe that starts with an unhacked 6.3a HR10-250?

I zippered my first HR10-250 with InstanctCake for the HR10-250 and the LBA48/Enhanced, and it is still sitting at 3.1.5f patiently waiting to be upgraded in the near future.

I procured a second unhacked HR10-250 over the weekend, activated it, got the 6.3a upgrade installed last night, and now that everything on it seems to be in working order, ready to pull the drive and add enhancements to it. I would like to just make it a 6.3b box to start and not re-image to 3.1.5f and work my way to 6.3b.

[aprest]

I am having a terrible time making cron and fakecall work after upgrading my HR10-250 STBs to 6.3b using Slicer. These HR10-250 STBs were hacked using Zipper and the enhancement script to get back from 6.3a to 3.1.5f and later sliced to 6.3b. I can run fakecall.tcl manually and see the changes in System Information and if I reboot I also see the changes in System Information. So fakecall is working in those circumstances but is not being implemented by cron at the times shown in /enhancements/varhacks/spool/cron/crontabs/root. In addition I don’t see a change in the time for the Scheduled Call after manually running fakecall (or rebooting) even though the Last Successful call time is updated. Interestingly I only see cron.test.out in /var/log on one HR10-250 but both cron.test.out and cronlog-main in the other HR10-250. In the HR10-250 that has cronlog-main I can see that TWP is being stopped and started, and cron.test.out being deleted, and the season pass backup being made, and logs wiped. But there is no evidence or indication that fakecall has run.

If I ran ps in TeraTermPro I see /busybox/crond is running. I have made the change in fakecall.tcl from “dbobj $ssobj set Complete 7” to try “{ dbobj $ssobj set Complete 7 } catch junk { }” (without the quotes).
I ran “echo 'root:x:0:0:root:/:/bin/sh' > /etc/passwd” and “echo 'root:x:0: ' > /etc/group” and checked the /etc/passwd and /etc/group to confirm the changes. Fakecall.tcl is shown in rc.sysinit.author and busybox is in the root as is crond:
# start crond after waiting 30 seconds
sleep 30
/busybox/crond

Today I tried rerunning tweak.sh on the unit that is missing the cronlog-main file and it ran fine and I again made the changes listed above but it didn’t help. I did notice however that running tweak.sh changed the root file in the enhancements/varhacks/spool/cron/crontabs directory. Stopping and starting TWP was missing after rerunning tweak.sh but fakecall and all othe sections were still present. I also noticed that there are several versions of the root file present in addition to the one in the enhancements/varhacks/spool/cron/crontabs directory.

I also noticed that some of the commands in rc.sysinit.author are redundant and are different between as those in rc.sysinit.author.bak and rc.sysinit.author.orig. It appears as though the redundancies were created when I sliced from 31.15f to 6.3b and agin when I reran tweak.sh. For example I now have two occurrences of “export TIVO root” and an additional “enhancements” in the PATH=. In addition the sections in rc.sysinit.author for starting netserver, EndPadPlus, TivoWebPlus, crond and “Check if var got wiped” are repeated at the end of the file. The additional “enhancements” and “start” section were created by rerunning tweak.sh. The redundant “export TIVO root” was created when I sliced to 6.3b.

Does anyone have any ideas what is going on and how I can fix it?

[NytOwl666]

My question may be in line with .-2

Replacement hacked drive for a HR10-250:

Pulled the latest everything from PTVupgrade, Zipper, Slicer, etc and burned the CD and built the drive. All pretty much went well. Network comes up, TW, etc. Did get error when I said yes to the gotomydvr though.

Everything was peachy, system info showed hack info, etc.

Then I felt brave. Sadness followed.

Ran slicer to bring to 6.3a. No errors.

On reboot it said it was installing an update and when it came back up it had lost all the hacks and net connectivity. It is 6.3a but not the hacked one.

Start over or is there a way to perhaps remove the drive and reapply the hacks and pop back in?

Not sure what I did wrong. 500GB drive works nice though...


Thx :confused:

[Finnstang]

I am having a terrible time making cron and fakecall work after upgrading my HR10-250 STBs to 6.3b using Slicer. These HR10-250 STBs were hacked using Zipper and the enhancement script to get back from 6.3a to 3.1.5f and later sliced to 6.3b. I can run fakecall.tcl manually and see the changes in System Information and if I reboot I also see the changes in System Information. So fakecall is working in those circumstances but is not being implemented by cron at the times shown in /enhancements/varhacks/spool/cron/crontabs/root. In addition I don’t see a change in the time for the Scheduled Call after manually running fakecall (or rebooting) even though the Last Successful call time is updated. Interestingly I only see cron.test.log in /var/log on one HR10-250 but both cron.test.log and cronlog-main in the other HR10-250. In the HR10-250 that has cronlog-main I can see that TWP is being stopped and started, and cron.test.out being deleted, and the season pass backup being made, and logs wiped. But there is no evidence or indication that fakecall has run.

If I ran ps in TeraTermPro I see /busybox/crond is running. I have made the change in fakecall.tcl from “dbobj $ssobj set Complete 7” to try “{ dbobj $ssobj set Complete 7 } catch junk { }” (without the quotes).
I ran “echo 'root:x:0:0:root:/:/bin/sh' > /etc/passwd” and “echo 'root:x:0: ' > /etc/group” and checked the /etc/passwd and /etc/group to confirm the changes. Fakecall.tcl is shown in rc.sysinit.author and busybox is in the root as is crond:
# start crond after waiting 30 seconds
sleep 30
/busybox/crond

Today I tried rerunning tweak.sh on the unit that is missing the cronlog-main file and it ran fine and I again made the changes listed above but it didn’t help. I did notice however that running tweak.sh changed the root file in the enhancements/varhacks/spool/cron/crontabs directory. Stopping and starting TWP was missing after rerunning tweak.sh but fakecall and all othe sections were still present. I also noticed that there are several versions of the root file present in addition to the one in the enhancements/varhacks/spool/cron/crontabs directory.

I also noticed that some of the commands in rc.sysinit.author are redundant and are different between as those in rc.sysinit.author.bak and rc.sysinit.author.orig. It appears as though the redundancies were created when I sliced from 31.15f to 6.3b and agin when I reran tweak.sh. For example I now have two occurrences of “export TIVO root” and an additional “enhancements” in the PATH=. In addition the sections in rc.sysinit.author for starting netserver, EndPadPlus, TivoWebPlus, crond and “Check if var got wiped” are repeated at the end of the file. The additional “enhancements” and “start” section were created by rerunning tweak.sh. The redundant “export TIVO root” was created when I sliced to 6.3b.

Does anyone have any ideas what is going on and how I can fix it?
So HR10-250 #1 only has the cron.test.out file but not the cronlog-main file? (I noticed in your post you said the cron.test.log file but it is really cron.test.out. Is that a typo or is your file named incorrectly?) Is cron.test.out getting time stamps? What is the contents of the file when you type root at the bash prompt? HR10-250 #2 you see both cron.test.out and cronlog-main files, and everything seems to be running except fakecall? Which copy of fakecall did you make the change to? The one being called in the root file? Have you tried running fakecall manually to see if it completes successfully? I would suggest downloading the latest AIO utilities over at DDB since it contains the latest version of fakecall that has been slimmed down and does not need to be edited.

ETA: If you get a blank file when you type root at the bash prompt, you need to run /enhancements/var-symlinks.sh to rebuild the symlinks in var.

[kimsan]

My question may be in line with .-2

Replacement hacked drive for a HR10-250:

Pulled the latest everything from PTVupgrade, Zipper, Slicer, etc and burned the CD and built the drive. All pretty much went well. Network comes up, TW, etc. Did get error when I said yes to the gotomydvr though.

Everything was peachy, system info showed hack info, etc.

Then I felt brave. Sadness followed.

Ran slicer to bring to 6.3a. No errors.

On reboot it said it was installing an update and when it came back up it had lost all the hacks and net connectivity. It is 6.3a but not the hacked one.

Start over or is there a way to perhaps remove the drive and reapply the hacks and pop back in?

Not sure what I did wrong. 500GB drive works nice though...


Thx :confused:

I had a similar expierience on one unit. Apparently no hacks after an apparent slicer failure that ended in an upgrade to 6.3b *despite* telling me it failed.

Try zippering the unit as a 101 vs the normal 357.

OR

First try using the TiVo UI itself to set up networking and assign the address.

No promises, but the first worked on my apparent blown upgrade and the second worked when I restored a hacked single image to a dual drive set.

YMMV.

[aprest]

So HR10-250 #1 only has the cron.test.out file but not the cronlog-main file? (I noticed in your post you said the cron.test.log file but it is really cron.test.out. Is that a typo or is your file named incorrectly?) Is cron.test.out getting time stamps? What is the contents of the file when you type root at the bash prompt? HR10-250 #2 you see both cron.test.out and cronlog-main files, and everything seems to be running except fakecall? Which copy of fakecall did you make the change to? The one being called in the root file? Have you tried running fakecall manually to see if it completes successfully? I would suggest downloading the latest AIO utilities over at DDB since it contains the latest version of fakecall that has been slimmed down and does not need to be edited.

ETA: If you get a blank file when you type root at the bash prompt, you need to run /enhancements/var-symlinks.sh to rebuild the symlinks in var.

I meant cron.test.log and made the correction in my original post. This morning I see both cron.test.out and cronlog-main in both HR10-250 STBs. In HR10-250 #2 that had both files I again see that TWP is being stopped and started, and cron.test.out being deleted, and the season pass backup being made, and logs wiped. It appears that fakecall worked last night at around 11:20 PM EST and the Next Scheduled moved a day. However cronlog-main does not show anything about fakecall being run. Nevertheless #2 might be working.

HR10-250 #1 that now does have both a cron.test.out and a cronlog-main it appears that it tried to make a call last night and failed and was scheduled to make a call this afternoon. Cronlog-main only shows cron.test.out being deleted. Cron.test.out is getting time stamps

I made the changes to the fakecall.tcl in/busybox. There is another version in /ptvupgrade/bin which isn't in the root. I ran /busybox/fakecall.tcl successfully and it showed:
Last Successful: Wednesday, January 10, 2007 at 6:58 AM
Last Attempt: Wednesday, January 10, 2007 at 6:58 AM
Last Attempt: Failed, No Dial Tone
Next Scheduled: Tuesday January 16, 2006 at 10:45 PM

I ran root at the bash and got:
Processing '//.joerc'...done
Processing '//.joerc'...done

IW /var/spool/cron/crontabs/ro Row 79 Col 57 12:23 Ctrl-K H for help
/var/log/cronlog-main

# Run fakecall every night at 10:20pm cst
20 4 * * * tivosh /busybox/fakecall.tcl

# Delete the crond log files every 3 months
22 9 1 */3 * rm /var/log/cronlog-main; echo "Date cron logs wiped">>
/var/log

# Delete cron.test.out every night at 3:24am cst
22 9 * * * rm /var/log/cron.test.out; echo "Date cron.test.out deleted" >>
/v

# Weekly reboots. Cleans things out for better performance if you have
several
# Also restarts logs, and allows fakecall to reset the last successful call
ind
# so your Tivo won't call home (fakecall doesn't update mfs entries without
a r
# This allows you to keep your phone line connected for callerID and PPV
orderi
# Run safereboot, so reboot only happens when nothing is recording.
** Joe's Own Editor v2.9.8-pre1 ** Copyright (C) 2001 **

There is a version of root in /enhancements and one in /enhancements/varhacks/spool/cron/crontabs which is twice as long and has a lot more commands. Which version of root should be running? Should I make changes to root so that they are the same? What initiates the running of root?

Incidentally I ran root on HR10-250 #2 and got:
Family Room Tivo-TiVo# root
Couldn't open '/tivo-bin/etc/joerc'

I had run /enhancements/var-symlinks.sh to rebuild the symlinks in var already on HR10-250 #2.

Thank you for your help.

[bigrig]

Looks like #2 doesn't have joe. Copy .joerc from the one tivo to the other. Put it in the root dir.

Also change the command in the crontab so it will log when fakecall is ran

# Run fakecall every night at 10:20pm cst
20 4 * * * tivosh /busybox/fakecall.tcl; echo "Date Fakecall Ran" >> /var/log

[aprest]

Looks like #2 doesn't have joe. Copy .joerc from the one tivo to the other. Put it in the root dir.

Also change the command in the crontab so it will log when fakecall is ran

# Run fakecall every night at 10:20pm cst
20 4 * * * tivosh /busybox/fakecall.tcl; echo "Date Fakecall Ran" >> /var/log


Thanks bigrig. I made the following change:

# Run fakecall every night at 10:20pm cst
20 4 * * * tivosh /busybox/fakecall.tcl; echo "`date` fakecall ran" >> /var/log/chronlog-main

This was consistent with the rest of the commands that report in chronlog-main.

There is a joe and a joe.tgz in /enhancements of both HR10-250 STBs. The files are identical between the two. Where is .joerc? I don't see it in either unit but one reports just fine when I run root from the bash. I am somewhat of a noobie but where is the root - is it just / ?

[gworkman]

Should have left "well enough" alone, but I didn't. Caller ID wasn't working. I ran tweak_uninstall.sh. Now, when I run sh tweak.sh, it downloads the script but during the extract process, it gives me a write error due to "No Space Left on Device".

What is safe to delete to provide the space needed for the script to untar the files?

[Lord Vader]

Try running e2fsck, which would free up space and clear out some errors.

[gworkman]

Thanks. This freed enough space to run the tweak. CID is working now.

[WeBoat]

I've been trying to get the 6.3b slices to load with dbload.

I had a new instantcaked drive (3.1.5f) and ran dbload and it appeard that it ran fine, but they never showed up with the echo command.

So I sliced the system up to 6.3a with slicer and I now have a stable 6.3a system.

echo mls /SwSystem | tivosh still shows:

Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
3.1.5f-01-2-357 tyDb 3180 01/10/07 20:56 676
6.3a-01-2-357 tyDb 53870 01/10/07 20:56 796
ACTIVE tyDb 53870 01/10/07 20:56 796

I've ftp'd the tarball over and extracted it into /var/packages

Now when I run dbload I get:

dbload: GZcore-84631465-2.slice
dbload (0x30042)

while executing
"dbload $db $file"
("foreach" body line 3)
invoked from within
"foreach file $argv {
puts "dbload: $file"
dbload $db $file
}"
(file "/tivo-bin/dbload" line 26)

Note: Only the core slice won't install. All the other slices seem to complete fine. Also, I've done this from scractch and rebooted and done it from scratch. Same error. The first time I did it from 3.1.5f it seemed to complete fine. Not since.

Has anyone seen this?

Thanks

[bpratt]

If anyone wants a mfsbackup of an unhacked 6.3b I discovered one at:
http://www.filefactory.com/file/7db266/

[Finnstang]

Thanks bigrig. I made the following change:

# Run fakecall every night at 10:20pm cst
20 4 * * * tivosh /busybox/fakecall.tcl; echo "`date` fakecall ran" >> /var/log/chronlog-main

This was consistent with the rest of the commands that report in chronlog-main.

There is a joe and a joe.tgz in /enhancements of both HR10-250 STBs. The files are identical between the two. Where is .joerc? I don't see it in either unit but one reports just fine when I run root from the bash. I am somewhat of a noobie but where is the root - is it just / ?
One part of fakecall actually doing its job, is to have the TiVo reboot after fakecall is run. Otherwise the system never looks at the new call-in date.

.joerc is in the root, which is /, in order to see it, you need to do ls -a (the -a will show hidden files and folders, which have the . before them)

[cartilage01]

I have been seeing a message on the TiVo since I upgraded to 6.3b. The message says something like:

"The copywrite holder of this program allows viewing in standard definition using component video."
This message appears on the info for the recorded program. My TV does not have HDMI inputs and the program looks noticably worse than the HD program. I have seen in now on ABC, NBC and CBS but not on all programs recorded. Is this the broadcast flag being enable as a feature for 6.3b? Is there a patch to get rid of it?

[Lord Vader]

If anyone wants a mfsbackup of an unhacked 6.3b I put one at:
http://www.filefactory.com/file/7db266/

So is this basically an "Instantcake" type virgin image of 6.3b in its entirety? Not slices, huh?

[rbautch]

If anyone wants a mfsbackup of an unhacked 6.3b I put one at:
http://www.filefactory.com/file/7db266/It's illegal to host a tivo image (which is copyrighted)...but don't take it down until I'm finished downloading it.

[Lord Vader]

It's illegal to host a tivo image (which is copyrighted)...but don't take it down until I'm finished downloading it.

;) ;)

[aprest]

One part of fakecall actually doing its job, is to have the TiVo reboot after fakecall is run. Otherwise the system never looks at the new call-in date.

.joerc is in the root, which is /, in order to see it, you need to do ls -a (the -a will show hidden files and folders, which have the . before them)


Thanks to your and bigrig's help I think I am making progress. fakecall ran on both HR10-250 STBs according to cronlog-main. Interestingly though it ran on both units at exactly the same time this morning at 4:28 AM EST according to System Information. The Next Scheduled call was also moved a day. I thought it was supposed to run at 11:20 PM EST. For some reason the log shows two occurrences of fakecall running at the same time on HR10-250 #1 and once on #2. In addition it appears the cronlog-main got wiped since there were no other reports in cronlog-main. I must wonder if there was a reboot on both units. Is there a way to tell if there was a reboot in any of the logs in TWP?

I ran ls -a on both units and do not see .joerc in either one and yet running root from the bash works on one and not the other - I get the same info that I previously pasted.

[bpratt]

So is this basically an "Instantcake" type virgin image of 6.3b in its entirety? Not slices, huh?
Yes.

[WeBoat]

Hopefully someone can help me...

I started over again on this tivo.

ptvnet and instacake two drives.
running 3.1.5f now

I move the 6.3b tarball over and put the .slice files in /var/packages
mount -o remount,rw /dev/hda7
dbload *.slice

it appears all the slices load correctly.

I've done this 3 times and waiting as long as two hours after dbload is finished and the 6.3b never shows up.

anything I might be missing?

I set the ptv flags to upgrade on. Also, originally the echo command showed 3.1.5e and 3.1.5f now only f shows up. but 6.3b never loads.

What could be keeping it from loading?

[sk33t3r]

If anyone wants a mfsbackup of an unhacked 6.3b I discovered one at:
http://www.filefactory.com/file/7db266/


Sux you have to have a login for that site. If someone put the file where I can get it easily I will put on with the resst of the file I have up on one of my sites.

[dswallow]

Sux you have to have a login for that site.
No you don't.

They just offer alternate ways to get to things; but you definitely can download that file without signing up for anything and without paying for anything.

[sk33t3r]

Aww yes, I didint read all the crap, I will put it up as soon as its done downloading.

[aprest]

I ran Is -a on both units and do not see .joerc in either one and yet running root from the bash works on one and not the other - I get the same info that I previously pasted.
I unzipped .joerc and FTP'd it to / and now if I type root at the bash it works.

[sk33t3r]

I have the 6.3b hr10-250 image up at http://www.jeanandrick.com/tivofiles/ go get it if you like. bpratt found it some where, I am merly offering a second site to download it from.

[dswallow]

I have the 6.3b hr10-250 image up at http://www.jeanandrick.com/tivofiles/ go get it if you like. bpratt found it some where, I am merly offering a second site to download it from.
font size="+7"?

:)

[solsurfer]

Here's an odd one - I zippered up my HR-10-250 and have been patiently awaiting the 6.3 upgrade, but it's been quite a while, and I've forgotten the ip address of the box. I think at the time I zippered it (3 months ago), static ip's were not possible for this unit, but I can't remember for sure. I do know it was working because I was able to plug it into my router from time to time to check for the slices.

Well, now that sk33t3r has made the 6.3 slices available, I thought I'd go ahead and do the upgrade. But when I plug the tivo into my router, it's not showing up in the dhcp client list, so I can't see it's ip address! I tried pinging several ips hoping to get lucky without success. What are my options now? Any way to figure out the ip?

If not, I'm assuming I could find my serial cable and use that - but I've never used that before. I'm sorry to say that I'm not even sure if that plugs directly into my pc, and how I would go about pinging the box? Do I just need to start from scratch?

Thanks,

Rod

[sk33t3r]

font size="+7"?

:)

Dswallow, no problem reading the text imy site is their???? :D


Solsurfer, to avoid forgetting the IP if each of my tivo's, I write the ip on the back with a perm marker. :D

And the slices are not mine, I am just making them available

[gworkman]

If Tivo is configured with an IP on your network, this program will find it for you.

http://www.angryziber.com/ipscan/

[solsurfer]

If Tivo is configured with an IP on your network, this program will find it for you.

http://www.angryziber.com/ipscan/

I think this worked, but now I can't telnet it. I can ping it, but I can't see it's name ( I may have re-named it.) I tried "telnet -t vt100 192.168.2.5" and "telnet 192.168.2.5". Any ideas?

[John_Hatchett]

If someone has managed to upgrade to 6.3b with backported usb networking, bash, and tivoftpd installed would you be willing to share an mfsbackup image with someone who trashed thiers in the attemp?

[solsurfer]

I think this worked, but now I can't telnet it. I can ping it, but I can't see it's name ( I may have re-named it.) I tried "telnet -t vt100 192.168.2.5" and "telnet 192.168.2.5". Any ideas?

I take it back - I think the new ip I was seeing was my laptop. The ethernet cable is getting green lights and showing activity, but no ip is registering. So I guess I'm back to square one. Can I buy a serial cable and attach directly to my pc? Or if I pull the drive and put it in the computer do I have to start from scratch?

[gworkman]

I had a similar issue with my Tivo when I upgraded from 3.xx to 6.3b. I had both power and link lights but couldn't find an IP address assigned to the Tivo. I had to run zipper on the PC twice to get it to work. During the zipper setup process, you plug in a static IP. Try pulling the drive and running the zipper process once or twice and see if you can get where you want to be.

I literally pulled the drive, ran zipper, installed in Tivo, repeated, then it worked. You may get lucky and only need one pull, but keep the cover open just in case.

Since 6.3b w/hacks, I've had no issues with my box at all.

[Elbozi]

I've spent 18 hours solid trying to fix my HR10-250 to get it to 6.3 using the Blasted USB200M version 2.1. I drove all over Dallas trying to find an older version or one on the compatible list, but no one carries them. The USB200M 2.1's are everywhere.

So I'm trying to make it work..

I'm using the latest Zipper with Slicer and I'm just not getting anywhere. I have read and searched hundreds of threads, here and on two other major forums to no avail.

The problem pops up in trying to get the backported drivers to install before rebooting with the sliced in 6.3.

I've seen some solutions posted on here, but they seem to relate more to PTVnet. and not Zipper?

I'm seeing that I should modify usb.map file in the /install/lib/modules

but when I install 6.3 (for the 10th time) I still don't have anything in the /install folder when I view it with my FTP software. I'm thinking it is because it is on another partition? And if so how the heck do I get to the other partition to make the changes before rebooting into 6.3?

What is the software or method to get this done. I'm a Linux Noob. But I got this far, I'm sure with a wee bit more help I can have it done.

[ibooyaka]

I've spent 18 hours solid trying to fix my HR10-250 to get it to 6.3 using the Blasted USB200M version 2.1. I drove all over Dallas trying to find an older version or one on the compatible list, but no one carries them. The USB200M 2.1's are everywhere.

So I'm trying to make it work..

I'm using the latest Zipper with Slicer and I'm just not getting anywhere. I have read and searched hundreds of threads, here and on two other major forums to no avail.

The problem pops up in trying to get the backported drivers to install before rebooting with the sliced in 6.3.

I've seen some solutions posted on here, but they seem to relate more to PTVnet. and not Zipper?

I'm seeing that I should modify usb.map file in the /install/lib/modules

but when I install 6.3 (for the 10th time) I still don't have anything in the /install folder when I view it with my FTP software. I'm thinking it is because it is on another partition? And if so how the heck do I get to the other partition to make the changes before rebooting into 6.3?

What is the software or method to get this done. I'm a Linux Noob. But I got this far, I'm sure with a wee bit more help I can have it done.

I have a DLink DUB-E100 vB1 (which is not supported by the stock 6.3 drivers). I use the zipper to image my drive to a fresh 3.1.5f, run the tweaks, and then use the slicer to upgrade to 6.3x

I follow post #1251 in this thread (Sorry can't post URLs yet)

So I press ctrl-c to exit the script instead of rebooting, and then run:

sh /var/packages/update2 6.3

this is related to ptvnet but it works fine with the zipper, it will download the latest usb drivers, reinstall TiVoWebPlus, and set DHCP.

After that I reboot, and I have never had a problem losing network connectivity.

[solsurfer]

OK - I solved my IP problem by re-sippering the drive (thanks, gworkman). But now I don't seem to be able to get the slices loaded properly. Anybody have any idea what I'm doing wrong here. It looks like the dbload is running properly, but I still don't show 6.3 in the echo.

rodshdtivo-TiVo# rw
mounting read write
rodshdtivo-TiVo# cd /var/packages
rodshdtivo-TiVo# tar -xf hr10_250_6.3bslices.tar
rodshdtivo-TiVo# dbload *.slice
dbload: GZcore-84631465-2.slice
dbload: GZhpk-Series2-84631469-2.slice
dbload: GZkernel-Series2-84631467-2.slice
dbload: swsystem-84631477-2.slice
dbload: utils-84631463-2.slice
rodshdtivo-TiVo# echo mls /SwSystem | tivosh
Directory of /SwSystem starting at ''

Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
3.1.5f-01-2-357 tyDb 206180 03/25/05 18:10 700
ACTIVE tyDb 206180 03/25/05 18:10 700

rodshdtivo-TiVo#

[Elbozi]

I follow post #1251 in this thread (Sorry can't post URLs yet)

So I press ctrl-c to exit the script instead of rebooting, and then run:

sh /var/packages/update2 6.3

this is related to ptvnet but it works fine with the zipper, it will download the latest usb drivers, reinstall TiVoWebPlus, and set DHCP.

After that I reboot, and I have never had a problem losing network connectivity.

Thanks for the reply! I was excited to try it out. But I'm still hitting a rock wall.

When i run the command:

sh /var/packages/update2 6.3

I get this: :(
diva-TiVo# sh /var/packages/update2 6.3
/var/packages/update2: /var/packages/update2: No such file or directory

So I ftp'd in and there is nothing in my /var/packages folder


..
So far I:
1. Created Zippered w/Slicer Install on a new 250 gig drive with a 160 gig slave
2. Loaded into the Tivo, telnetted in and ran cd /hacks; sh tweak.sh
Installed everything except the netperf install
3. Went through the various reboot cycles
4. Everything is good, can run TivoWeb, Telnet, FTp, I get my locals etc
5. Log in again to run slicer with the command:
/hacks/slicer 6.3b-01-2-357

It does it's thing fine, and then I CNTRL-C to get out of rebooting


I don't know how I don't have the /var/packages/update 6.3
is it something I can download ? It seems it should have gotten installed
when I ran the Slicer. I am using the latest slicer, it seems that this should have
installed it.

Okay Update.. I was thinking I would rerun the slicer.. Perhaps I screwed things up more.. this is log of what happened..


diva-TiVo# /hacks/slicer 6.3b-01-2-357

The Slicer - Version 1.4

WARNING!! We are about to install 6.3b-01-2-357 software on your TiVo
Once you start this process, there is no way to restore your
previous software version without re-imaging. Before you begin,
we suggest you make a backup image of your hard drive, and read
the forums at tivocommunity.xxx and *************.xxx that
pertain to The Slicer.

Hit <enter> to continue, or <cntrl-c> to exit:
Great! Here we go...

Your root filesystem partition is hda7
Your kernel partition is hda6
Your alternate root filesystem partition is hda4
Your alternate kernel partition is hda3

6.3b-01-2-357 software slices are correctly loaded and ready to install.
Hit <enter> to continue, or <cntrl-c> to exit:

Checking your system for required utilities...
find is present
wget is present
tar is present
sed is present
cut is present
All required binaries are present. Proceeding...

Editing installSw.itcl

Installing new software. This will take several minutes...

installSw.itcl failed to set up your new partitions. Please
run /tvbin/installSw.itcl manually to pinpoint the error.
Also check to see if installSw.itcl was edited properly.
Since your bootpage was not flipped, you will not lose your
existing hacks if you reboot, and The Slicer may safely be
run again. Exiting now...
diva-TiVo#

[rbautch]

I've spent 18 hours solid trying to fix my HR10-250 to get it to 6.3 using the Blasted USB200M version 2.1. I drove all over Dallas trying to find an older version or one on the compatible list, but no one carries them. The USB200M 2.1's are everywhere.

So I'm trying to make it work..

I'm using the latest Zipper with Slicer and I'm just not getting anywhere. I have read and searched hundreds of threads, here and on two other major forums to no avail.

The problem pops up in trying to get the backported drivers to install before rebooting with the sliced in 6.3.

I've seen some solutions posted on here, but they seem to relate more to PTVnet. and not Zipper?

I'm seeing that I should modify usb.map file in the /install/lib/modules

but when I install 6.3 (for the 10th time) I still don't have anything in the /install folder when I view it with my FTP software. I'm thinking it is because it is on another partition? And if so how the heck do I get to the other partition to make the changes before rebooting into 6.3?

What is the software or method to get this done. I'm a Linux Noob. But I got this far, I'm sure with a wee bit more help I can have it done.The drivers installed by the Zipper do not support the usb200m v1.2, so mount the old partition will not help. Plenty of compatible adapters on Ebay. Otherwise download Jamies latest drivers and install them using a serial connection or by pulling the drive.

[Elbozi]

The drivers installed by the Zipper do not support the usb200m v1.2, so mount the old partition will not help. Plenty of compatible adapters on Ebay. Otherwise download Jamies latest drivers and install them using a serial connection or by pulling the drive.

Thanks very much for the reply.. I know you meant usb200m v2.1.

Question 1: I know your the Zipper expert, but how did Ibookya in post #1379 pull it off using the process from post #1251 of this thread?

Question 2: What program is placing the update2 6.3 in the /var/packages folder? I was thinking it was part of the InstantCake SE/with Slicer 1.4, which were both used in my Zipper install.

Question 3: If I try to pull the hard drive, how do you get access to it? Do you have to use a boot Disc? Or will windows See it?

Question 4: I'm looking around, where do I find Jamie's USB drivers?
Answered my own question, the drivers are from JamieP
Search the DDB forum for the following zip file.

usbobj-4.27-20051226

I believe it is under the post titled "Backport drivers" or similar. I'm not sure how to attach the file here, otherwise I would do so. The files are dated 12/26/2005.

Make sure you use the ones from the 2.4.20 folders, and use "Series 2" for the host files.

[ibooyaka]

Ok I've been battling with my HR10-250 all weekend.

I've finally got it upgraded to 6.3b (zippered to 3.1.5f then to 6.3b using the slicer). I have everything working so far on 6.3b, and have manually applied the tivoapp patches to enable the backdoors, etc.

The only thing now is when I try to record a show, it tells me I need to make a "test call" before I can use DVR service functions. This also shows up when I go to the NPL. I've tried to run fakecall manually and in system information it says it worked, but I still get that screen to make a test call. Any way to clear this without starting over? Thanks

[rbautch]

Thanks very much for the reply.. I know you meant usb200m v2.1.

Question 1: I know your the Zipper expert, but how did Ibookya in post #1379 pull it off using the process from post #1251 of this thread?

Question 2: What program is placing the update2 6.3 in the /var/packages folder? I was thinking it was part of the InstantCake SE/with Slicer 1.4, which were both used in my Zipper install.

Question 3: If I try to pull the hard drive, how do you get access to it? Do you have to use a boot Disc? Or will windows See it?

Question 4: I'm looking around, where do I find Jamie's USB drivers?1. That process uses wget to download new drivers - presumably these are Jamie's latest drivers that support the usb200m v2.1.

2. update2 is not a program or a file. It's an argument used when running the slicer that tells it to download new drivers.

3. You need a boot disk or a Linux computer. If you're at this level, it's going to take some time and reading to get where you need to be to install the drivers you need. That's great if you're up for it, otherwise I suggest getting a different adapter.

4. Jamies drivers are posted on DDB, a website that cannot be linked to from this forum.

[solsurfer]

OK - I solved my IP problem by re-sippering the drive (thanks, gworkman). But now I don't seem to be able to get the slices loaded properly. Anybody have any idea what I'm doing wrong here. It looks like the dbload is running properly, but I still don't show 6.3 in the echo.

rodshdtivo-TiVo# rw
mounting read write
rodshdtivo-TiVo# cd /var/packages
rodshdtivo-TiVo# tar -xf hr10_250_6.3bslices.tar
rodshdtivo-TiVo# dbload *.slice
dbload: GZcore-84631465-2.slice
dbload: GZhpk-Series2-84631469-2.slice
dbload: GZkernel-Series2-84631467-2.slice
dbload: swsystem-84631477-2.slice
dbload: utils-84631463-2.slice
rodshdtivo-TiVo# echo mls /SwSystem | tivosh
Directory of /SwSystem starting at ''

Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
3.1.5f-01-2-357 tyDb 206180 03/25/05 18:10 700
ACTIVE tyDb 206180 03/25/05 18:10 700

rodshdtivo-TiVo#

I tried mounting using a command line I found in an earlier DarthOverlord post, too: mount -o remount,rw /dev/hda7. No luck. Any ideas/suggestions?

Thanks!

[JWThiers]

I tried mounting using a command line I found in an earlier DarthOverlord post, too: mount -o remount,rw /dev/hda7. No luck. Any ideas/suggestions?

Thanks!
That command just enables write mode on the tivo drive /hda7.

[solsurfer]

That command just enables write mode on the tivo drive /hda7.

Yeah, I know, but since the dbload seems to be running against the slices (based on the output I showed above), I figured maybe the problem was it wasn't actually writing the data? Or maybe it's not running all of the slices?

[Finnstang]

Thanks to your and bigrig's help I think I am making progress. fakecall ran on both HR10-250 STBs according to cronlog-main. Interestingly though it ran on both units at exactly the same time this morning at 4:28 AM EST according to System Information. The Next Scheduled call was also moved a day. I thought it was supposed to run at 11:20 PM EST. For some reason the log shows two occurrences of fakecall running at the same time on HR10-250 #1 and once on #2. In addition it appears the cronlog-main got wiped since there were no other reports in cronlog-main. I must wonder if there was a reboot on both units. Is there a way to tell if there was a reboot in any of the logs in TWP?

I ran Is -a on both units and do not see .joerc in either one and yet running root from the bash works on one and not the other - I get the same info that I previously pasted.
I realize you already have joe working, but just to let you know, the ls -a command is a lower case L not an upper case I, which is why you didn't see the .joerc file on the working one. In TWP under the system info screen, you can see the uptime which would be the time since the last reboot.

[aprest]

I realize you already have joe working, but just to let you know, the ls -a command is a lower case L not an upper case I, which is why you didn't see the .joerc file on the working one.

Actually I did run ls -a and not Is -a
In my post I made the "I" typo. Now that I FTP'd .joerc to the root of the "non-working unit", typing root at the bash works but typing ls -a at the bash does not show .joerc - it does show DEADJOE on one unit no evidence of .joerc on the other unit. It could be that .joerc is in a different directory. Since the joe editor is working on both units it doesn't really matter.


Now crond on both units is running perfectly. I will need to adjust the starting time for safereboot since it shows that the unit was busy when it tried to reboot at 3:25am cst Monday morning. I think that one of the other commands has not been completed when it attempts to do the safereboot because if I manually run safereboot.tcl it works.

Thanks again!

[bigrig]

I think Safereboot only reboots if it's not recording a show.

So you FTP'd .joerc into the root dir but then it doesn't show with ls -a? Doesn't make any sense. But I'm glad things are working for ya.

Matt

[Finnstang]

When you do the ls -a in the root, look all the way at the top of the list and you should see .joerc sitting there next to .profile

[slydog75]

Ok, I downloaded the tarball from Sk33t3rs webpage and FTPd it into /var/packages and then unzipped it with tar -vxf. The rest is below:



HDTivo-TiVo# pwd
/var/packages
HDTivo-TiVo#
HDTivo-TiVo# ls
GZcore-84631465-2.slice hr10_250_6.3bslices.tar
GZhpk-Series2-84631469-2.slice swsystem-84631477-2.slice
GZkernel-Series2-84631467-2.slice utils-84631463-2.slice
HDTivo-TiVo#
HDTivo-TiVo# bootpage -p
No device name given, assuming /dev/hda
root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false
HDTivo-TiVo#
HDTivo-TiVo# mount -o remount,rw /dev/hda4
HDTivo-TiVo#
HDTivo-TiVo# dbload *.slice
dbload: GZcore-84631465-2.slice
dbload (0x30042)

while executing
"dbload $db $file"
("foreach" body line 3)
invoked from within
"foreach file $argv {
puts "dbload: $file"
dbload $db $file
}"
(file "/busybox/dbload" line 26)
HDTivo-TiVo#
HDTivo-TiVo#

Any ideas why I'm getting this error when I try to run dbload?

[solsurfer]

Ok, I was able to install 6.3b using the slices sk33t3r posted, and following DarthOverloard's instructions to the letter. I had done so previously, but this in tha past I used the tar file and an different ftp program. I switched to the rar file and uploaded them using SmartFTP and somewhere in the mix, that fixed it and 6.3b was dbloaded and the slicer upgraded the system. I now have folders!

I was hoping to report complete success, but at during the slicer I did get this message: "don't forget to run the /enhancements/var-symlinks.sh script after you reboot to re-establish your symlinks in var." Well, I plugged the tivo into the tv, and re-booted just to make sure the 6.3b worked (it did). But it no loger had 30 sec skip funtionality, and in looking at the system info backdoors no loger seemed to be enabled. So I tried tel-netting into it again, to run that script. But now when I attempt to access the box I get no ping response. I'm using the FA120. What now? Can I pull the drive and run the zipper on top of 6.3b?

[ibooyaka]

Ok, I was able to install 6.3b using the slices sk33t3r posted, and following DarthOverloard's instructions to the letter. I had done so previously, but this in tha past I used the tar file and an different ftp program. I switched to the rar file and uploaded them using SmartFTP and somewhere in the mix, that fixed it and 6.3b was dbloaded and the slicer upgraded the system. I now have folders!

I was hoping to report complete success, but at during the slicer I did get this message: "don't forget to run the /enhancements/var-symlinks.sh script after you reboot to re-establish your symlinks in var." Well, I plugged the tivo into the tv, and re-booted just to make sure the 6.3b worked (it did). But it no loger had 30 sec skip funtionality, and in looking at the system info backdoors no loger seemed to be enabled. So I tried tel-netting into it again, to run that script. But now when I attempt to access the box I get no ping response. I'm using the FA120. What now? Can I pull the drive and run the zipper on top of 6.3b?

I think with 6.3b, you have to manually patch the tivoapp to enable the backdoors, 30 second skip, disable encryption, etc.

/enhancements/var-symlinks.sh just rebuilds the symlinks in /var/hack/

Not sure why you lost telnet access though. Looks like there is a new 6.3x version of the zipper, that may help a lot of people who want to use 6.3b.

[rbautch]

Ok, I was able to install 6.3b using the slices sk33t3r posted, and following DarthOverloard's instructions to the letter. I had done so previously, but this in tha past I used the tar file and an different ftp program. I switched to the rar file and uploaded them using SmartFTP and somewhere in the mix, that fixed it and 6.3b was dbloaded and the slicer upgraded the system. I now have folders!

I was hoping to report complete success, but at during the slicer I did get this message: "don't forget to run the /enhancements/var-symlinks.sh script after you reboot to re-establish your symlinks in var." Well, I plugged the tivo into the tv, and re-booted just to make sure the 6.3b worked (it did). But it no loger had 30 sec skip funtionality, and in looking at the system info backdoors no loger seemed to be enabled. So I tried tel-netting into it again, to run that script. But now when I attempt to access the box I get no ping response. I'm using the FA120. What now? Can I pull the drive and run the zipper on top of 6.3b?The current version of the Zipper doesn't support 6.3 software, but if you're feeling brave, you could try the beta version I posted last night, which does. You can also pull your drive and check your author file to make sure you have the proper commands to set network params in MFS. These commands should be surrounded by if/then statements that make sure the network.tcl script only runs the first time you boot.

[slydog75]

Sk33t3r, there appears to be a curropted file in your tarball that was causing my problem. I tried again using the rar file and it worked great.

[solsurfer]

The current version of the Zipper doesn't support 6.3 software, but if you're feeling brave, you could try the beta version I posted last night, which does. You can also pull your drive and check your author file to make sure you have the proper commands to set network params in MFS. These commands should be surrounded by if/then statements that make sure the network.tcl script only runs the first time you boot.

I can give the beta a try. (I'm assuming the likelihood of compete melt-down is low ;-).) Where did you post it? Just follow the same instructions from http://www.mastersav.com/tivo_zipper.html but use this new file?

I'll check the author file while I'm at it. What do I type once I mount the drive to see that?

Thanks, rbautch!

[slydog75]

I can give the beta a try. (I'm assuming the likelihood of compete melt-down is low ;-).) Where did you post it?

http://www.tivocommunity.com/tivo-vb/showthread.php?t=336697

[slydog75]

Just chiming in with another successful update to 6.3b. I used the rar files from Sk33t3rs website and the slicer.

[solsurfer]

I pulled the drive and ran the beta zipper. That part worked fine, and I assigned the same ip address as the drive previously had. But when I put it back into the tivo and tried to telnet, I still could not access it. I can ping the ip, but whenever I try to telnet I get a "could not open connection to the host, on port 23" error. I pulled the drive and re-ran the cdrom script assigning a new ip - same problem. I also tried assigning an ip out of the dhcp range of the router. That gave me no ping, and no telnet. Any advice? Now I have folders but no 30 sec skip! Not worth the trade off :-(

[rbautch]

If you can ping it but cant telnet to it, that usually means there is a firewall or other program preventing communication.

[solsurfer]

Success! When I ran the beta, I answered yes to the questions about wireless and filled in my security settings (with the intention of testing that later for you). I then turned off WEP on the router and plugged the tivo into via an ethernet cable. That's when I was having the trouble. But after your last post, I re-zippered the drive, I answered no to wireless, and turned WEP back on the router, and it worked.

Thanks to you and everyone else for the help! I'll try to test the wireless on the beta later this week, and will keep you posted if any issues crop up.

[MurrayW]

Just chiming in with another successful update to 6.3b. I used the rar files from Sk33t3rs website and the slicer.I did exactly the same thing last night and all went well! Thanks to all who contribute here.
Murray

[falstaffpac]

I've spent a lot of time over the past 36 hours reading, trialing, and fighting with my HD Tivo, getting it upgraded. I have the Linksys 200m adapter, which complicated the issue. I tried a ton of different recommendations found on this forum and the other forum, not of which solved my problems. The jist of my experience was conflicts which kept cropping up from having PTVNet installed. For me, the solution was to get rid of PTVNET. For those of you still trying to get everything going and don't mind starting from scratch, here is how I managed it. I can't offer support for this, I don't know nearly enough. I hope it helps save someone some time. To do this, you must have a serial cable. Thanks for all the help guys, everything below I learned from reading through the threads.

Instantcake 6.3a SE the drive(s)
Zipper the drive (you should now have network access)
Drop the HD(s) in the Tivo and boot

Telnet and remove the ptvupgrade directory entirely
mount -o remount,rw / (make disc read/writeable)
rm -r /ptvupgrade (removes /ptvupgrade and subdirectories)
rm -r /init (removes the init directory)
rm /test.conf (removes the test.conf file in root)

FTP the 5 6.3b *.slice files to /var/packages (optional step, if you have the slices, otherwise you can just slice whatever version you have available)

/var/packages/dbload *.slice
echo mls /SwSystem | tivosh (get available software versions)
./slicer <software_version>
Reboot

Now network has been lost, must use serial cable:
/hacks/tweak.sh (implement desired options, install USB 2.0 drivers)
Reboot (Adapter should light up after this reboot)

Network still not accessible at this point, use serial cable:
/enhancements/net-launch.sh
Set your parameters
Reboot

You should now have telnet, FTP via network

-----------------------------------
DISABLE ENCRYPTION, ENABLE 30-SECOND SKIP, BACKDOORS, AND HMO/HME

rw
cp /tvbin/tivoapp /tvbin/tivoapp.orig
cd /tvbin
mv tivoapp tivoapp.tmp
cp tivoapp.tmp tivoapp
chmod 755 tivoapp

#encryption
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=1602412
#30 sec skip
echo -ne "\x10\x40\x00\x2b" | dd conv=notrunc of=tivoapp bs=1 seek=6713220
#Enable backdoors
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=2804900
#HMO/HME
echo -ne "\x34\x11\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=903436
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=1118524
echo -ne "\x10\x00\x00\x14" | dd conv=notrunc of=tivoapp bs=1 seek=5724672


#Cron stuff which I don't understand, but seems important
echo 'root:x:0:0:root:/:/bin/sh' > /etc/passwd
echo 'root:x:0: ' > /etc/group

reboot

One unusual observation, I didn't have TWP initially after gaining network access. After I installed the backdoors, etc and rebooted again, TWP is up and running. At any rate, everything seems to be working.

[JWThiers]

Thanks for the walkthru. You might to post it on the wiki as well. See my sig.

[slydog75]

rw
cp /tvbin/tivoapp /tvbin/tivoapp.orig
cd /tvbin
mv tivoapp tivoapp.tmp
cp tivoapp.tmp tivoapp


I"m no unix expert, but isn't this creating TWO backups of tivoapp and then replacing the original tivoapp with the second copy?

[Da Goon]

These commands make a backup of tivoapp (tivoapp.orig) and then move the temp tivoapp around so the filesystem will allow you to write changes to it. Usually after doing this I delete the tivoapp.tmp file since it's not needed anymore and just takes up space. You can patch tivoapp without making the tivoapp.orig, but the other steps are absolutely required if you want the changes to take effect. If you don't take these steps then you will most likely get a "text file busy" error and the patches won't do anything.

[Finnstang]

Yeah...I usually just do something like this:
rw
cd /tvbin
mv tivoapp tivoapp.orig
cp tivoapp.orig tivoappThen do the echo statements. Assuming everything works, I delete the file or ftp it back to my pc.

[MurrayW]

Well I successfully upgraded my hacked HR10-250 from to 6.3b as I reported yesterday. So last night I decided to activate the 30 second skip, enable backdoors and disable encryption following a post another user reported many pages back in this thread or possibly in the "other" forum. Here is what I entered verbatim (I checked each line about 5 times before hitting return each time):

cd /tvbin
cp tivoapp tivoapp.6.3.orig
cp tivoapp tivoapp.mod
#[30 Second Skip]
echo -ne "\x10\x40\x00\x2b" | dd conv=notrunc of=tivoapp.mod bs=1
seek=6713220
#[Enable backdoors]
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp.mod bs=1
seek=2804900
#[Disable Encryption]
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp.mod bs=1
seek=1602412
rm tivoapp
mv tivoapp.mod tivoapp
chmod 755 tivoapp
reboot

I see in falstaffpac's post (a few up from this one), that he starts out with RW which I wondered about when I was doing mine, but didn't see his post before I started. I assumed (you know what that means) that if I didn't mount it as RW then just nothing would happen and I would have to start again. Also, I was wondering about the comments such as #[Enable backdoors] if I really needed to type them in my telnet session but I did (again assuming the worst case was me typing a few extra characters).

As I was entering these commands I got messages back such as 4 in and 4 out (not exactly, but something like that) so I assumed things were working fine. I rebooted and this is where I realized I had problems. The HR10-250 stayed in the "Almost there..." screen forever. I let it chug away for about 2 hours, then manually rebooted it and let it go overnight. This morning it was still on the same screen.

So obviously I screwed something up and want to find out how to recover and what to do once I get back to the state I was in Wednesday night and am ready to attempt this again.

Recovery Options
I am thinking that because it won't finish booting (so I can't telnet into it -- I couldn't do it even with a serial cable could I?), that my only option is to pull the drives. After pulling the drives, is there a way that I can copy the backup copy tivoapp.6.3.orig back to tivoapp and put it back into the HR10-250 or do I need to start all over from scratch and re-zipper it?

Applying Patches Once I get a bootable HR10-250 again, what do I need to do differently to apply the patches successfully.

thanks,
Murray

[falstaffpac]

Since you had boot problems, I triple checked the tivoapp patch commands just to make sure I didn't have a typo. The commands I listed are 100% consistent with commands listed in 2 other posts in this thread.

I COPY/PASTED my walkthrough from a txt file I was maintaining. The #comment lines were just so I knew what the patches were doing. They don't need to be entered in at bash, sorry for the confusion.

After applying the tivoapp patches, reboot was standard, taking less than 5 minutes. Sounds like something else may have happened on your end. After looking at your quote of the text, it looks like some commands are out of order. What you quoted shows that your are chmodding tivoapp after applying the patches. I'm not sure if you are quoting what I posted, but your commands appear out of order compared to mine. Of course, it is equally possible mine are out of order, as I simply duplicated the information from another post. But I can confirm on my end that at HMO option shows up on the menu.

[dswallow]

cd /tvbin
cp tivoapp tivoapp.6.3.orig
cp tivoapp tivoapp.mod
#[30 Second Skip]
echo -ne "\x10\x40\x00\x2b" | dd conv=notrunc of=tivoapp.mod bs=1
seek=6713220
#[Enable backdoors]
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp.mod bs=1
seek=2804900
#[Disable Encryption]
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp.mod bs=1
seek=1602412
rm tivoapp
mv tivoapp.mod tivoapp
chmod 755 tivoapp
reboot


You didn't put the "seek=..." stuff on separate lines, did you? That ought to be at the end of the echo lines. Just want to make sure it isn't something simple.

The following is what I did on 3 HR10-250's and all came out OK.

cp /tvbin/tivoapp /tvbin/tivoapp.orig
cd /tvbin

mv tivoapp tivoapp.tmp
cp tivoapp.tmp tivoapp
chmod 755 tivoapp


#No encryption
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=1602412


#30-second skip
echo -ne "\x10\x40\x00\x2b" | dd conv=notrunc of=tivoapp bs=1 seek=6713220


#Backdoors
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=2804900


#HMO/HME
echo -ne "\x34\x11\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=903436
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=1118524
echo -ne "\x10\x00\x00\x14" | dd conv=notrunc of=tivoapp bs=1 seek=5724672


mount -o remount,ro /
reboot


#(after reboot, clean up)
cd /tvbin
rm tivoapp.tmp

[MurrayW]

You didn't put the "seek=..." stuff on separate lines, did you? That ought to be at the end of the echo lines. Just want to make sure it isn't something simple.

The following is what I did on 3 HR10-250's and all came out OK.

cp /tvbin/tivoapp /tvbin/tivoapp.orig
cd /tvbin

mv tivoapp tivoapp.tmp
cp tivoapp.tmp tivoapp
chmod 755 tivoapp


#No encryption
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=1602412


#30-second skip
echo -ne "\x10\x40\x00\x2b" | dd conv=notrunc of=tivoapp bs=1 seek=6713220


#Backdoors
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=2804900


#HMO/HME
echo -ne "\x34\x11\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=903436
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=1118524
echo -ne "\x10\x00\x00\x14" | dd conv=notrunc of=tivoapp bs=1 seek=5724672


mount -o remount,ro /
reboot


#(after reboot, clean up)
cd /tvbin
rm tivoapp.tmpDoug, yes I did put the seeks on separate lines! :o So the #No encryption, etc. are actually entered in during the telnet session?


falstaffpac, I didn't get that code from you. I took it from another user...I didn't see your post until this morning when I had already done my damage -- so I can't blame you for my ignorance. :D

So on to my recovery question. Is there a way I can put the drives into a PC and copy my original tivoapp back or am I better off just starting the whole re-zippering process over again?

Thanks for the help!

Murray

[dswallow]

Doug, yes I did put the seeks on separate lines! :o So the #No encryption, etc. are actually entered in during the telnet session?


falstaffpac, I didn't get that code from you. I took it from another user...I didn't see your post until this morning when I had already done my damage -- so I can't blame you for my ignorance. :D

So on to my recovery question. Is there a way I can put the drives into a PC and copy my original tivoapp back or am I better off just starting the whole re-zippering process over again?

Thanks for the help!

Murray
The lines with "#" are just comments.

Based on what you said you did you did make a copy of the original file as part of your steps, so you could put the drive in another computer and boot from a linux CD, mount that partition and then:

cd /tvbin
cp tivoapp.6.3.orig tivoapp

(where "/tvbin" would be replaced with the full mounted location of the folder/partition)

[MurrayW]

The lines with "#" are just comments.

Based on what you said you did you did make a copy of the original file as part of your steps, so you could put the drive in another computer and boot from a linux CD, mount that partition and then:

cd /tvbin
cp tivoapp.6.3.orig tivoapp

(where "/tvbin" would be replaced with the full mounted location of the folder/partition)Thanks for all your help...but I am going to ask 1 more question! :D

I just want to make sure I am absolutely clear on this...when you say the lines with # are just comments, does that mean you still type them in on the telnet line? Are they added to the tivoapp file you are modifying as comments? Sorry for asking what may be a dumb question, but after screwing this up once, I want to make sure I leave nothing to chance in my interpretaion.

thanks,
Murray

[dswallow]

I just want to make sure I am absolutely clear on this...when you say the lines with # are just comments, does that mean you still type them in on the telnet line? Are they added to the tivoapp file you are modifying as comments? Sorry for asking what may be a dumb question, but after screwing this up once, I want to make sure I leave nothing to chance in my interpretaion.
No, you don't need to type them in. But since they begin with a "#" they'll be ignored by the bash shell if you did type them in. So, to be clear, don't type them in. It'd just be a waste of your time. :)

[MurrayW]

I am still struggling to get my 1st hacked HR10-250 to upgrade to 6.3b with most of the hacks I had before...I am going to start over again (for the 3rd time). On 2 of my 3 HR10-250's I got the 6.3b software by running the add63 script in the late November time frame. My 3rd one never got updated (this is the 1st one I was attempting to upgrade to 6.3b). I took the image from Sk33t3rs webpage. I don't think that there is anything wrong with the images, but just incase it somehow got corrupted in the download or transfer process I want to try a different one. Can I just ftp one of the 6.3b images sitting on HR10-250 #1 or #2 and transfer it to the same directory on HR10-250 #3 then run the slicer?

thanks,
Murray

[Lord Vader]

You can't just ftp the image. You'll need to get the slices into mfs then use Slicer to upgrade. Note that many people have reported total loss of connectivity, serial included, when doing this. Your best bet to go to 6.3b is, if you have no recordings to worry about saving, to get Instantcake 6.3b, which is the complete image.

[John_Hatchett]

Murray,

pull the drive, download http://www.filefactory.com/file/7db266/ to get a 6.3b base image, add it into rbautch's beta zipper for 6.3b as 000001 and answer yes to zipper's prompt to install the image.

After getting past some cd burning issues this worked for me.

John

[sk33t3r]

I have the same image up here (http://jeanandrick.com/tivofiles/v63b.rar)

[MurrayW]

I have the same image up here (http://jeanandrick.com/tivofiles/v63b.rar)sk33t3r, That's where I got my current image! :D As I said, I am sure that my problems were not image related, but I just wanted to try another source to rule that out completely. It looks like my problems are related to having uppercase names for a couple of my files the zipper is trying to use...I am going to try again tonight with lowercase names and RBautch's beta zipper and hope all goes well.

thanks,
Murray

[MurrayW]

Murray,

pull the drive, download http://www.filefactory.com/file/7db266/ to get a 6.3b base image, add it into rbautch's beta zipper for 6.3b as 000001 and answer yes to zipper's prompt to install the image.

After getting past some cd burning issues this worked for me.

JohnJohn, since you live in Austin, do you want to trade me your working HR10-250 for my "broken" one? :D :D

Thanks for the suggestions.

Murray

[John_Hatchett]

If getting the units swapped with directv wasn't such a hassle I'd consider it. If you want, I'd be happy to image and zipper your hr10-250, or just a drive, if you can leave it with me for a day later this week.

[MurrayW]

If getting the units swapped with directv wasn't such a hassle I'd consider it. If you want, I'd be happy to image and zipper your hr10-250, or just a drive, if you can leave it with me for a day later this week.John, I was just kidding! Thanks for the generous offer. I've got to work this out myself, it shouldn't be this hard. If for some reason I am still in this same shape a week from now, I may take you up on your offer!

thanks,
Murray

[John_Hatchett]

Don't wait until superbowl weekend :) Seriously , I still have the cover off HR10-250 #2 and the PC so it would only take an hour or so to image another drive and boot up the unit to make sure everything installed ok. Only challenge I see is that the network addresses I would set for my house would probably be different than yours and we would have to work around that.

[sk33t3r]

Upgrading 3.15f To 6.3b Without Using The Slicer And With Some Hacks To Start.

Step 1 – Took a blank 250 GB Seagate Drive and ran the Zipper to restore the 3.15f image I made from my original HR10-250 drive.

Step 2 – Ran the Zipper to apply the hacked kernel and set up networking. Reinstalled drive into HR10-250. It ran through the setup, reboot partially into satellite scan, then went through the normal startup process.

Step 3 – Telnet into Tivo. Use SmartFTP to install slices obtained here - http://www.jeanandrick.com/tivofiles. Thanks sk33t3r. Upload slices to var/packages
Go into telnet. Run
mount -o remount,rw /dev/hdax

(where x is either 7 or 4), use the command
bootpage –p
to figure it out which is the active partition.

Step 4 – Make sure you are in the /var/packages directory and enter
dbload *.slice

Now wait about ten minutes for the slices to be put together. Then enter:
echo mls /SwSystem | tivosh

I then followed rbautch’s recommendations:



This next part I have to give credit to kehrli from DVR ground where you play.

• Edit /tvbin/installSw.itcl and find
exec /var/utils/updateroot /dev/hda /install /var/packages >&@ stdout
change it to
exec /var/utils/updateroot /dev/hda /install /var/packages $name >&@ stdout
A few lines further down, find reboot
change that to exit 0
The first change is needed or the script will not run to completion. The 2nd change prevents the reboot from occurring so we can install our hacks in the new root artition.
• Run bootpage -p. This will give you where your current root partition is located. It should be either /dev/hda7 or /dev/hda4. TiVo uses two pairs of partitions for loading its software. One pair is active with the current software version. Then if you upgrade your software, it'll get loaded to the other pair, and then that pair becomes active. The bootpage command will tell you which drive partition is being used for the TiVo's file system root. If you then run bootpage -b it will tell you the current boot partition (the partition where your Linux kernel lives). The pairs are set up as one of the following: root=/dev/hda7 boot=/dev/hda6 OR root=/dev/hda4 boot=/dev/hda3. Write down the results from the bootpage command. You MUST know your root and boot partitions prior to proceeding. You must not get these wrong. Some rare bootpage documentation is supplied at the bottom of this document.
• Run installSw.itcl 6.3b-01-2-357. This should run to completion and not leave you with error messages, telling you which files and line numbers had the errors. If you get errors, one of the earlier steps is wrong and you'll need to find and fix it. Not well: the software version number in the command above may be slightly different. Get the exact string to enter by using echo mls /SwSystem | tivosh

This last part also took about ten minutes. I then proceeded to reboot my HR10-250, since I was not trying to keep any hacks.

The HR10-250, went through a semi-long update about 15 minutes or so. Viola, I now had an update system with 6.3b running. Beautiful folders, ahhhh!!!!

Step 5 – Replacing the virgin 6.3b kernel with the hacked kernel.

I basically took the drive out and ran the zipper again. The only problem was that I was getting this message:

The file /tivo /etc/resolv.conf is missing
The file /cdrom /etc/resolv.conf is missing

So when I tried the drive in the Tivo, I could not for the life of me get into the bash prompt or telnet in. I then was given this advice by dswallow:


So I followed his directions, by putting the drive back in the computer,

I ran the following:

1. Created a mount point for the partition and mount it:
mkdir /mnt/mnt4
mount /dev/hda4 /mnt/mnt4
2. Changed to the directory that will house rc.sysyinit.author
cd /mnt/mnt4/etc/rc.d
3. Editted rc.sysinit.author:
pico rc.sysinit.author


#!/bin/bash
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10
tnlited 23 /bin/bash -login &
tivoftpd
route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0
fakecall.tcl

/bin/bash </dev/ttyS2&> /dev/ttyS2&
#insmod /lib/modules/usbcore.o
#insmod /lib/modules/ax8817x.o
sleep 60
#ifconfig eth0 192.168.0.175 netmask 255.255.255.0
#route add default gw 192.168.0.1
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
mount -o remount,ro /

#call network.tcl
/hacks/network.tcl 192.168.0.175 192.168.0.1
fi
fi

I then hit ctrl x and saved it. Then I edited this part:
cd /mnt/mnt4/sbin



cd /sbin
mv iptables iptables.old
echo -e '#!/bin/bash\nexit 0' > iptables
chmod 755 iptables
Then I reinserted the drive, allowed it to boot up once, then I rebooted and viola – bash prompt appeared and I am able to telnet.

The problem now is my bash prompt works, but does not respond to ‘ls’ or ‘./’ commands. I can change directories and gzip and some other things, but not some of the basic linux commands. Any help would be much appreciated.


One other thing you can do to get the tarball of slices loaded is from /var/packages run the following;

wget http://www.jeanandrick.com/tivofiles/hr10_250_6.3bslices.tar

this will download the tarball to what ever directory you run it from then you can extract the tar ball with tar -xf *.tar then after than dbload *.slice which may take a while to run, then proceed as stated above.

[Da Goon]

I definitely prefer the method above for software updates. It doesn't cost a thing, and doesn't take that long at all to do. Also, if something screws up, troubleshooting can be much easier, since you typed the commands, you know what was done, instead of blindly letting a script do it in the background for you.
"Teach a man to fish..." so to speak.

[Runch Machine]

After downloading the slices from the site shown above, running the tar -xf command on the file and the running dbload *.slice, I get the following error:
HDTiVo2-bash# echo mls /SwSystem | tivosh
Directory of /SwSystem starting at ''

HDTiVo2-bash# cd /var
HDTiVo2-bash# cd packages
HDTiVo2-bash# ls
HDTiVo2-bash# ls
HDTiVo2-bash# rw
mounting read write
HDTiVo2-bash# ls
hr10_250_6.3bslices.tar
HDTiVo2-bash# tar -xf hr10_250_6.3bslices.tar
HDTiVo2-bash# ls
GZcore-84631465-2.slice hr10_250_6.3bslices.tar
GZhpk-Series2-84631469-2.slice swsystem-84631477-2.slice
GZkernel-Series2-84631467-2.slice utils-84631463-2.slice
HDTiVo2-bash# dbload *.slice
dbload: GZcore-84631465-2.slice
dbload (0x30042)

while executing
"dbload $db $file"
("foreach" body line 3)
invoked from within
"foreach file $argv {
puts "dbload: $file"
dbload $db $file
}"
(file "/busybox/dbload" line 26)
HDTiVo2-bash# echo mls /SwSystem | tivosh
Directory of /SwSystem starting at ''

Name Type FsId Date Time Size
---- ---- ---- ---- ---- ----
6.3a-01-2-357 tyDb 1523286 09/24/06 04:50 796
ACTIVE tyDb 1523286 09/24/06 04:50 796

HDTiVo2-bash#


Any ideas why or how to proceed?

[WhyMe]

I keep losing my caller id. I tried both ways zippered 3.1 and then sliced to 6.3 and zippered 6.3....Any suggestions...Thanks Michael

[archer-55]

My upgrade from ptv 3.1.5f to 6.3.2b went fine, once I grabbed the slices from .rar instead of the .tar. The tar has a bad file. Had to get rar and dbload, which needed 7zip.
Bought slicer. Cheap at $20. Much easier than the steps people are doing to save the money.

Got the slices, ran dbload, ran slicer. rebooted and was networked. applied the patches to tivoapp. rebooted. Now have usual patches (non-encrypt, 30 sec skip..), plus home media access to photos and music. Press 2 on list to get folders, 1 for sorted by name.
It sees my other units (MRV), but does not actually get a list from them.

get slices from rar at the site listed in earlier posts

Uncompress the rar on windows to get the slices.
Ftp'd them to tivo into \var\packages
dbload \var\packages\*.slices
slicer 6.3b-01-2-357
reboot
patch tivoapp
reboot

Did it all by network with touching my unit in its entertainment center. Very nice.

[PJO1966]

My upgrade from ptv 3.1.5f to 6.3.2b went fine, once I grabbed the slices from .rar instead of the .tar. The tar has a bad file. Had to get rar and dbload, which needed 7zip.
Bought slicer. Cheap at $20. Much easier than the steps people are doing to save the money.

Got the slices, ran dbload, ran slicer. rebooted and was networked. applied the patches to tivoapp. rebooted. Now have usual patches (non-encrypt, 30 sec skip..), plus home media access to photos and music. Press 2 on list to get folders, 1 for sorted by name.
It sees my other units (MRV), but does not actually get a list from them.

get slices from rar at the site listed in earlier posts

Uncompress the rar on windows to get the slices.
Ftp'd them to tivo into \var\packages
dbload \var\packages\*.slices
slicer 6.3b-01-2-357
reboot
patch tivoapp
reboot

Did it all by network with touching my unit in its entertainment center. Very nice.


Thanks for the summary for us newbies! That's a great first post. I've gotten to the point where I have dbloaded the slices and they are finally showing up under SWSystem. Before I go any farther I just need to make sure I know what to do to prevent losing connection through my Airlink ASOHOUSB. My search continues.

[PJO1966]

I ran into a bit of a problem. After the slicer was done, I went to hit ctrl-c and the TiVo rebooted. I did indeed lose network connectivity, but I was able to connect using the serial cable. First I tried to mount the Alt Root, but I got a "can't find" message. After doing some reading I tried the process in post 1251. The update downloaded. AngryIP was unable to find the TiVo, and it looks like the lights on the Airlink ASOHOUSB were not on. I tried re-running tweak.sh with no luck. From what I can tell, my next course of action is to pull the drive and run the zipper again.

The good news is that 6.3b installed successfully and I have folders and the faster speed when navigating.

If anyone has any suggestions on what to try before I pull the drive tomorrow, I'm all ears.

[Runch Machine]

My upgrade from ptv 3.1.5f to 6.3.2b went fine, once I grabbed the slices from .rar instead of the .tar. The tar has a bad file. Had to get rar and dbload, which needed 7zip.
Bought slicer. Cheap at $20. Much easier than the steps people are doing to save the money.

Got the slices, ran dbload, ran slicer. rebooted and was networked. applied the patches to tivoapp. rebooted. Now have usual patches (non-encrypt, 30 sec skip..), plus home media access to photos and music. Press 2 on list to get folders, 1 for sorted by name.
It sees my other units (MRV), but does not actually get a list from them.

get slices from rar at the site listed in earlier posts

Uncompress the rar on windows to get the slices.
Ftp'd them to tivo into \var\packages
dbload \var\packages\*.slices
slicer 6.3b-01-2-357
reboot
patch tivoapp
reboot

Did it all by network with touching my unit in its entertainment center. Very nice.

Thanks so much for your contribution! I did this and it works. I want to point out a typo for others: The dbload command if done in the var/packages directory is dbload *.slice. Don't put an s on the end of the word slice since the files all end with the word "slice" not "slices" .

Also don't forget to set the access to read/write by using the rw command.

[Da Goon]

I ran into a bit of a problem. After the slicer was done, I went to hit ctrl-c and the TiVo rebooted. I did indeed lose network connectivity, but I was able to connect using the serial cable. First I tried to mount the Alt Root, but I got a "can't find" message. After doing some reading I tried the process in post 1251. The update downloaded. AngryIP was unable to find the TiVo, and it looks like the lights on the Airlink ASOHOUSB were not on. I tried re-running tweak.sh with no luck. From what I can tell, my next course of action is to pull the drive and run the zipper again.

The good news is that 6.3b installed successfully and I have folders and the faster speed when navigating.

If anyone has any suggestions on what to try before I pull the drive tomorrow, I'm all ears.

The adapter you're using requires backported drivers, and IIRC the Slicer documentation states that it doesn't copy over these drivers for you. The drivers required are : echi-hcd.o , pegasus.o, usbcore.o, usbnet.o and usb-ohci.o. You should be able to pull the drive and copy these drivers from your old partition to your new, or even do it via serial, so long as you mount the partitions correctly. You'll have the original versions of these drivers already on your new root partition, so make sure to back them up just in case.
Also, make sure to add : product 0b95 7720 Airlink ASOHOUSB to your /etc/hotplug/usb.map under the "device usbnet" header. Reboot with adapter connected and your network should be back.

I've done this myself via serial connection during manual uprades 2x, and it worked like a charm, using the same ASOHOUSB adapter that you're using.

[Blackfoot]

The adapter you're using requires backported drivers, and IIRC the Slicer documentation states that it doesn't copy over these drivers for you. The drivers required are : echi-hcd.o , pegasus.o, usbcore.o, usbnet.o and usb-ohci.o. You should be able to pull the drive and copy these drivers from your old partition to your new, or even do it via serial, so long as you mount the partitions correctly. You'll have the original versions of these drivers already on your new root partition, so make sure to back them up just in case.
Also, make sure to add : product 0b95 7720 Airlink ASOHOUSB to your /etc/hotplug/usb.map under the "device usbnet" header. Reboot with adapter connected and your network should be back.

I've done this myself via serial connection during manual uprades 2x, and it worked like a charm, using the same ASOHOUSB adapter that you're using.

This is the first post I have seen where it tells me what to modify in the usb.map file. Excuse my ignorance with the following. I've messed up my previous tivo's before and lost all my recordings and don't want that to happen again.

I plan to upgrade from 3.1.5f to 6.3b using the slicer but haven't found clear and exact newb steps for copying the backported drivers. I have a LinkSys USB200m v2 adapter. Are there any step by steps instructions to follow to copy these over just prior to a reboot?

[Da Goon]

There aren't any "step-by-step" instructions so far that I've seen. You need to add your adapter's name and prod/vend numbers in the usb.map under the "device usbnet" header.

The drivers you need are in /lib/modules on your old partition and you need to copy them to /lib/modules on your new partition. Type bootpage -p to find out what your root partition is, and make sure to back up your original drivers.

I'd be very wary of giving "step-by-step" directions on this process, since in doing this it helps VERY MUCH to understand exactly what it is that you are doing. Search around a bit, here and at the "other forum" and you should be able to get what you need out of this. If not, get a serial cable and run Rbautch's tweak script that way, and it will take care of everything for you.

[Blackfoot]

There aren't any "step-by-step" instructions so far that I've seen. You need to add your adapter's name and prod/vend numbers in the usb.map under the "device usbnet" header.

The drivers you need are in /lib/modules on your old partition and you need to copy them to /lib/modules on your new partition. Type bootpage -p to find out what your root partition is, and make sure to back up your original drivers.

I'd be very wary of giving "step-by-step" directions on this process, since in doing this it helps VERY MUCH to understand exactly what it is that you are doing. Search around a bit, here and at the "other forum" and you should be able to get what you need out of this. If not, get a serial cable and run Rbautch's tweak script that way, and it will take care of everything for you.

Ok. Stupid questions. And I know it's because I am very rusty with this. I can find the /lib/modules on my active partition by using SmartFTP. Typing bootpage -p at a bash prompt gives me root=/dev/hda7. So my inactive partition must be hda4.

How do I mount the inactive partition to copy the drivers over?

Where do I find the usb.map file?

Are the 5 files noted in the previous post the same for LinkSys as the Airlink?

Should I choose to run the tweak.sh script file. Would I let the slicer complete and reboot, then when tivo is back up and running connect in on the serial port and run the script? Anything special to get the serial prompt up? Or is it like a cisco console screen? It just appears during bootup.

Sorry for all the questions, that I could probably find throughout the other threads, I'm just fearful of loosing all my recordings like I did when the S1 DTivo's for the surprise 3.5 update. That was a cold day with the wife.

[Da Goon]

If you're at 3.1.5f now, you're bootpage will get flipped when you update. The usb.map is in /etc/hotplug. All five drivers I listed need to be copied over. How were you planning on upgrading? Manually, slicer??

[MurrayW]

I have 3 HR10-250's and had difficulty re-zippering and re-hacking my first one, but I got through it basically by starting fresh -- lost all my recorded shows which for the 1st one was not a big deal.

I thought I would do better on the 2nd one, but am having problems again. I hope to get it all sorted out by the time I move my 3rd one up to 6.3.b since that is the only one with recordings that I really want to make sure that I keep.

My 2nd HR10-250 has 2 500G drives in it and was running 3.1.5f, zippered and hacked and behaving normally. 6.3b-01-2-357 had been downloaded into /SwSystem folder and I used the slicer to upgrade to 6.3b. Everything went well and I had 6.3b running with some of my hacks gone. This is what I did next:


Downloaded the latest zipper (2.8) and burned an iso.
Connected the master drive from the TiVo and hooked it up to my PC.
Booted off the zipper CD, ran the zipper and responded "yes" to save recordings.
Hooked the master drive back up to my TiVo along with the slave drive.
Booted the TiVo. Was able to telnet into the TiVo.
Moved to the /hacks directory and ran sh tweak_uninstall.sh
Ran sh tweak.sh -- at this point I got no response at all. The telnet session just remained blank. I waited for about 10 minutes, then rebooted and tried again with the same non-responsiveness.
Any ideas on what I am doing wrong so that I can make this work when I upgrade the software on my 3rd HR10-250? Also any suggestions on how to recover my 2nd one from this state of limbo (without starting over again from scratch would be appreciated).

thanks,
MurrayW

[Lord Vader]

Don't bother w/ 6.3b because that's moot. 6.3c is now the most recent version.

[MurrayW]

Don't bother w/ 6.3b because that's moot. 6.3c is now the most recent version.Well, I don't have 6.3c yet, but I doubt that my current problems are caused by 6.3b. It is most likely something I have done wrong and somewhere along the line I must have corrupted a file that keeps tweak.sh from running properly and I'd like to get this figured out for when I do upgrade to 6.3c.

[Blackfoot]

If you're at 3.1.5f now, you're bootpage will get flipped when you update. The usb.map is in /etc/hotplug. All five drivers I listed need to be copied over. How were you planning on upgrading? Manually, slicer??
I plan to purchase the slicer. I could probably manually do the work, but why when someone has written a script that makes it easier on you?

At the end of the slicer, I plan to cancel it, mount my hda4 and hda7 partitions. copy the 5 files listed using the cp command. Extract the usb.map file using SmartFTP, edit it and put it back. Then copy it to the /etc/hotplug location on the inactive partition.

What was the command again to mount the partitions from a telnet session?

And if I copy the files from \dev\hda7\lib\modules to \dev\hda4\lib\modules, will they be over written by anything? Say from the \install location?

[Finnstang]

mount /dev/hda7 /mnt to mount /dev/hda7 to the /mnt directory.

If you are going to copy the drivers while doing the slicer before rebooting, you just need to copy them into the /install directory though. You need to mount the other partition to get them if you reboot and complete the slicer upgrade.

[PJO1966]

I just tried to upgrade to 6.3c using the Slicer and got this:

Installing new software. This will take several minutes...

installSw.itcl failed to set up your new partitions. Please
run /tvbin/installSw.itcl manually to pinpoint the error.
Also check to see if installSw.itcl was edited properly.
Since your bootpage was not flipped, you will not lose your
existing hacks if you reboot, and The Slicer may safely be
run again. Exiting now...

Also, I just wanted to confirm... when I go to 6.3c I will once again lose the drivers for my Airlink ASOHOUSB, correct?

[Blackfoot]

mount /dev/hda7 /mnt to mount /dev/hda7 to the /mnt directory.

If you are going to copy the drivers while doing the slicer before rebooting, you just need to copy them into the /install directory though. You need to mount the other partition to get them if you reboot and complete the slicer upgrade.

I tried to mount /dev/hda4 to /mnt but I get an error that I must specify the filesystem type.

[MurrayW]

Well, I don't have 6.3c yet, but I doubt that my current problems are caused by 6.3b. It is most likely something I have done wrong and somewhere along the line I must have corrupted a file that keeps tweak.sh from running properly and I'd like to get this figured out for when I do upgrade to 6.3c.If I successfully had both drives working before re-zipperring, I shouldn't neet to use mfsadd -x -r 4 /dev/hdx /dev/hdx again after re-zipperring to make tweak.sh work again should I? The number of SD and HD hours that are showing up as available are correct for the 2 drive system.

Any ideas on what I am doing wrong that keeps tweak.sh from running correctly (seems to be in an endless loop -- Ctrl C will stop it and bring me back to the bash prompt) would be greatly appreciated.
thanks,
Murray

[Finnstang]

I tried to mount /dev/hda4 to /mnt but I get an error that I must specify the filesystem type.
I just did a telnet to my HR10 and typed the following:mount /dev/hda4 /mnt and it worked fine.

[Bobblob]

I got the same error as PJO1966 when trying to upgrade to 6.3c with slicer, but interestingly when I run installSw.itcl manually, it has no problems (and flips the bootpage, which I then flipped back manually.) When I try to diff the .itcl with the .orig, there are no differences. Not sure where to go from here...

[Blackfoot]

I just did a telnet to my HR10 and typed the following:mount /dev/hda4 /mnt and it worked fine.
Works fine on the SAT-T60, but not on my HR10. I do notice that TWP is not responding, so maybe I need a reboot.

bash-2.02# mount /dev/hda4 /mnt
mount: you must specify the filesystem type
bash-2.02#

[Cure]

My HR10-250 was imaged with a 3.15f InstantCake, zippered and sliced to 6.3a before the 6.3 Zipper was released. I've been pretty lucky, so I'm scared to keep doing things to it. Should I slice to 6.3c with the downloaded slices or leave it be? Will it upgrade on its own and overwrite my hacks?

I know Lord Vader and others have had tragic experiences going to 6.3b.

[Lord Vader]

Indeed I have. D@#$ Jedi tricks!

[rbautch]

My HR10-250 was imaged with a 3.15f InstantCake, zippered and sliced to 6.3a before the 6.3 Zipper was released. I've been pretty lucky, so I'm scared to keep doing things to it. Should I slice to 6.3c with the downloaded slices or leave it be? Will it upgrade on its own and overwrite my hacks?

I know Lord Vader and others have had tragic experiences going to 6.3b.If you let it upgrade on it's own, hacks will indeed be overwritten. Of course, you'd need to change your bootpage paramters before that will happen. If you don't upgrade, bad things will eventually start happening, like your tivo rebooting every night, or Tivo cutting off your guide data. Jedi experience notwithstanding, slice upgrades are generally harmless for most people. If you use the Slicer, there's less chance a typo or bad command with screw things up for you. Does your adapter require backported drivers?

[pdawg17]

I have 6.3c listed in SwModule but 6.3b (current) in SwSystem...what does this mean?

[dswallow]

I have 6.3c listed in SwModule but 6.3b (current) in SwSystem...what does this mean?
It means you're running 6.3b but 6.3c is there waiting for the signal from DirecTV to install it.

[rbautch]

I got the same error as PJO1966 when trying to upgrade to 6.3c with slicer, but interestingly when I run installSw.itcl manually, it has no problems (and flips the bootpage, which I then flipped back manually.) When I try to diff the .itcl with the .orig, there are no differences. Not sure where to go from here...You'll need to do a few things from here before rebooting:
1. Copy the killhdinitrd'd kernel from your old kernel partition to your new one:
dd if=/dev/hdaX of=/dev/hdaY bs=1024 count=2048where X and Y are you old and new kernel partitions.

2. Mount the new root filesystem somewhere like /install:
mount /dev/hdaZ /installwhere Z is your new root filesystem partition.

3. Copy your author file and any hacks from the old root filesystem to the new one.

4. If required by your adapter, copy backported drivers and usb.map from old root filesystem to the new one.

5. Fix iptables on new root filesystem.

6. Reboot.

It's possible that the slicer might do some or all this for you if you re-run it, but I'm not sure. I'm going to try an upgrade tonight and see if I can provide any additional insight.

[pdawg17]

It means you're running 6.3b but 6.3c is there waiting for the signal from DirecTV to install it.

But shouldn't 6.3c be listed in SwSystem with 6.3b (but with 6.3b listed as active)?

[vertigo235]

OK so since 6.3c is supposidly requried for DST, I guess I finally have to upgrade from 3.5xxx, I know that x ammount of this thread is completely worhtless and out of date, is there any way I can make sure that I'm going to upgrade with slicer without reading the entire 1456 posts? A good starting point? Can someone summarize the steps for me? Has it allready been done somewhere in this thread?

Thank you much.

[Lord Vader]

If you let it upgrade on it's own, hacks will indeed be overwritten. Of course, you'd need to change your bootpage paramters before that will happen. If you don't upgrade, bad things will eventually start happening, like your tivo rebooting every night, or Tivo cutting off your guide data. Jedi experience notwithstanding, slice upgrades are generally harmless for most people. If you use the Slicer, there's less chance a typo or bad command with screw things up for you. Does your adapter require backported drivers?

I'm not worried about losing the hacks because I can just reaplly them manually--stuff like encryption, 30-sec. skip, etc. is easy to fix. What is the big problem for me is the total loss of connectivity via both bash and serial. I've never been able to figure out why that happens to me and a few others but not to most.

[rbautch]

I'm not worried about losing the hacks because I can just reaplly them manually--stuff like encryption, 30-sec. skip, etc. is easy to fix. What is the big problem for me is the total loss of connectivity via both bash and serial. I've never been able to figure out why that happens to me and a few others but not to most.Not that the Zipper supports 6.3, I think the risk is substantially reduced. Worst case is pulling the drive and running the Zipper.

[rbautch]

You'll need to do a few things from here before rebooting:
1. Copy the killhdinitrd'd kernel from your old kernel partition to your new one:
dd if=/dev/hdaX of=/dev/hdaY bs=1024 count=2048where X and Y are you old and new kernel partitions.

2. Mount the new root filesystem somewhere like /install:
mount /dev/hdaZ /installwhere Z is your new root filesystem partition.

3. Copy your author file and any hacks from the old root filesystem to the new one.

4. If required by your adapter, copy backported drivers and usb.map from old root filesystem to the new one.

5. Fix iptables on new root filesystem.

6. Reboot.

It's possible that the slicer might do some or all this for you if you re-run it, but I'm not sure. I'm going to try an upgrade tonight and see if I can provide any additional insight.I just ran my upgrade with the Slicer, and worked fine. Depending on your willingness to pull the drive, an alternative to the above steps is to just run the Zipper on your drive.

[MurrayW]

Not meaning to be too impatient :) , but if anyone knows how I can troubleshoot this, I would be happy.
tweak.sh is stuck (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4864780&&#post4864780)
thanks,
Murray

[Blackfoot]

Works fine on the SAT-T60, but not on my HR10. I do notice that TWP is not responding, so maybe I need a reboot.

bash-2.02# mount /dev/hda4 /mnt
mount: you must specify the filesystem type
bash-2.02#
After a reboot, I still have the same issue. I poked around a bit and noticed that I have 2 versions of mount. The generic one in the /bin directory and a busybox version in the /ptvupgrade/busybox directory. Typing mount /dev/hda4 /mnt does not work using either mount. The generic one gives me the 'you must specify the filesystem' while the busybox gives me a 'mount: Mounting /dev/hda4 on /mnt failed: Invalid argument' error. What's odd is that I can mount /dev/hda7 to /mnt. But hda3, 6 or 4 all fail.

Obviously this could be an issue for a manual upgrade. I'm also assuming this would prevent the Slicer from doing it's job too. Any ideas?

[jkast]

Just re-installed the zipper on my hr10-250 after allowing it to upgrade itself to 6.3b. Everything seemed to go well. BUT what happened to the WebRemote? I see the webremote.itcl module in the TivoWebPlus/modules directory -- but it does not appear on any menu I see in the application. Anyone know how to get it back?

[rbautch]

Not meaning to be too impatient :) , but if anyone knows how I can troubleshoot this, I would be happy.
tweak.sh is stuck (http://www.tivocommunity.com/tivo-vb/showthread.php?p=4864780&&#post4864780)
thanks,
MurrayDo you have trouble running any shell script, or just tweak.sh? Try navigating to the directory it's in, and run it with ./tweak.sh

[rbautch]

After a reboot, I still have the same issue. I poked around a bit and noticed that I have 2 versions of mount. The generic one in the /bin directory and a busybox version in the /ptvupgrade/busybox directory. Typing mount /dev/hda4 /mnt does not work using either mount. The generic one gives me the 'you must specify the filesystem' while the busybox gives me a 'mount: Mounting /dev/hda4 on /mnt failed: Invalid argument' error. What's odd is that I can mount /dev/hda7 to /mnt. But hda3, 6 or 4 all fail.

Obviously this could be an issue for a manual upgrade. I'm also assuming this would prevent the Slicer from doing it's job too. Any ideas?For what it's worth, I can mount 4 and 7 using /bin/mount on my HR10-250. 3 and 6 give the "specify filesystem.." error. This is expected behavior since 3 and 6 do not contain valid filesystems, but kernels. Is it possible that you overwrote hda4 with a kernel? The sure fire test would be to copy hda7 to hda4 with dd if=/dev/hda7 of=/dev/hda4
...then try to mount hda4. If you're in the middle of an upgrade, this could fubar your tivo, but you'd know for sure.

[rbautch]

I've attached a program to the original post of this thread that copies your backported drivers and usb.map for your current filesystem to your new filesystem during a slice upgrade. Run it after the Slicer, but before rebooting. If your upgrading from 3.1.5f, you'll also need to manually modify the usb.map file in /platform/etc/hotplug of your new root filesystem. I've tested it only lightly, so use it at your own risk.

[Lord Vader]

Thanks, Russ. BTW, you might want to change the date of that update. You're still stuck in 2006. I'd like to forget that year if you don't mind. :p

[Blackfoot]

For what it's worth, I can mount 4 and 7 using /bin/mount on my HR10-250. 3 and 6 give the "specify filesystem.." error. This is expected behavior since 3 and 6 do not contain valid filesystems, but kernels. Is it possible that you overwrote hda4 with a kernel? The sure fire test would be to copy hda7 to hda4 with dd if=/dev/hda7 of=/dev/hda4
...then try to mount hda4. If you're in the middle of an upgrade, this could fubar your tivo, but you'd know for sure.
Nice!!!!! That did the trick.
bash-2.02# dd if=/dev/hda7 of=/dev/hda4
262144+0 records in
262144+0 records out
bash-2.02#
bash-2.02# mount /dev/hda4 /mnt
bash-2.02#
And FWIW, no I didn't copy any kernels to this partition. I built the drive using InstantCake in July 06 and its been running 3.1.5f ever since. No upgrades or anything. Of course now I can start my 6.3c upgrade. Thanks rbautch.

[Cure]

If you use the Slicer, there's less chance a typo or bad command with screw things up for you. Does your adapter require backported drivers?

Russ -

No, I have a FA120! Do I just slice with the 6.3c upgrade that came automatically?

[MurrayW]

Do you have trouble running any shell script, or just tweak.sh? Try navigating to the directory it's in, and run it with ./tweak.shI have no problems running tweak_uninstall.sh. I first ran tweak_uninstall.sh when I put my rezippered drive(s) back in the HR10-250 and then tried running it one or two times later when the tweak.sh didn't work. It gave me normal prompts and messages, so I think it ran fine. I think that tweak.sh is running because I never get a return bash prompt (looks to me like it is in some stalled state). I'll give the ./tweak.sh method a try tonight.

Do you think that these problems are somehow related to a 2-drive system? What is the recommended sequence of events to re-zipper a 2-drive system? Have others successfully re-zippered a 2-drive system? This is what I did starting with my already hacked 2-drive 3.1.5.f system:



Used the slicer to update to 6.3b -- everything minus some hack functionality seemed fine.
Re-zippered my master drive using version 2.8 of the zipper.
Put my master back into my HR10-250, reconnected all cables and booted -- I could channel surf, watch previously recorded shows and do other things that indicated my TiVo was still working.
Ran tweak_uninstall.sh. Got normal prompts and messages.
Ran tweak.sh. Never got any messages or prompts and never got the bash prompt back.
Rebooted or Ctrl-C to get the bash prompt back.
TiVo still has normal basic functionality -- channel changing, watching previously recorded shows, record new ones, etc. but has not hacks.


I shouldn't need to put both of my drives back into my PC and mfsadd them again should I? I am pretty sure I tried that when I had the problems updating my first 2-drive HR10-250 a couple of weeks ago and I had no luck. I ended up starting all over from scratch and losing my recordings for my first system. I can do that for the 2nd system also if I need to, but my 3rd system has recorded shows that I do not want to lose, so I really want to get this figured out before I tackle that one.
thanks,
Murray

[rbautch]

Russ -

No, I have a FA120! Do I just slice with the 6.3c upgrade that came automatically?Yes. run the slicer and you're done.

[rbautch]

I have no problems running tweak_uninstall.sh. I first ran tweak_uninstall.sh when I put my rezippered drive(s) back in the HR10-250 and then tried running it one or two times later when the tweak.sh didn't work. It gave me normal prompts and messages, so I think it ran fine. I think that tweak.sh is running because I never get a return bash prompt (looks to me like it is in some stalled state). I'll give the ./tweak.sh method a try tonight.

Do you think that these problems are somehow related to a 2-drive system? What is the recommended sequence of events to re-zipper a 2-drive system? Have others successfully re-zippered a 2-drive system? This is what I did starting with my already hacked 2-drive 3.1.5.f system:

1. Used the slicer to update to 6.3b -- everything minus some hack functionality seemed fine.
2. Re-zippered my master drive using version 2.8 of the zipper.
3. Put my master back into my HR10-250, reconnected all cables and booted -- I could channel surf, watch previously recorded shows and do other things that indicated my TiVo was still working.
4. Ran tweak_uninstall.sh. Got normal prompts and messages.
5. Ran tweak.sh. Never got any messages or prompts and never got the bash prompt back.
6. Rebooted or Ctrl-C to get the bash prompt back.
7. TiVo still has normal basic functionality -- channel changing, watching previously recorded shows, record new ones, etc. but has not hacks.


I shouldn't need to put both of my drives back into my PC and mfsadd them again should I? I am pretty sure I tried that when I had the problems updating my first 2-drive HR10-250 a couple of weeks ago and I had no luck. I ended up starting all over from scratch and losing my recordings for my first system. I can do that for the 2nd system also if I need to, but my 3rd system has recorded shows that I do not want to lose, so I really want to get this figured out before I tackle that one.
thanks,
MurrayYou shouldn't have to re-marry the drives after an upgrade. The only thing I can think of is that your Tivo is busy doing other things, and is just running the script very slowly. Try running it again, but just leave it run for several minutes.

[MurrayW]

You shouldn't have to re-marry the drives after an upgrade. The only thing I can think of is that your Tivo is busy doing other things, and is just running the script very slowly. Try running it again, but just leave it run for several minutes.I let it run for at least 1 hour one time before I gave up and Ctrl C'd it. Also, immmediately before or after I attempt to run tweak.sh, I have run tweak_uninstall.sh and it starts messaging and prompting me within seconds. In theory, is there anything wrong with my upgrade process and the order that I am doing them?
thanks,
Murray

[rbautch]

No, nothing wrong with the order. Perhaps the file is corrupted. Try FTPing a new tweak.sh to your tivo.

[MurrayW]

Do you have trouble running any shell script, or just tweak.sh? Try navigating to the directory it's in, and run it with ./tweak.shRuss, No change when I tried ./tweak.sh. I ftp'd a new copy of tweak.sh into my hacks director and tried running it. This time I got this message immediately after it started running ": command not found". The script then hung (I let it go for about 15 minutes before I Ctrl C'd it to stop to get back to the bash prompt. I'm going to pull the drive and rezipper it again tonight unless you can think of anything else for me to try -- like maybe try running the commands individually that the tweak.sh script runs to see if I can see where it is hanging?

Murray

[Lord Vader]

Russ,

Is it your recommendation to use Slicer, then BEFORE rebooting, rerun tweak.sh to make sure hacks are still there? I wanted to doublecheck before slicing to 6.3c, since some folks, myself included, seem to always lose all connectivity--serial and bash--when slicing from one version to the next.

[rbautch]

Is it your recommendation to use Slicer, then BEFORE rebooting, rerun tweak.sh to make sure hacks are still there? I wanted to doublecheck before slicing to 6.3c, since some folks, myself included, seem to always lose all connectivity--serial and bash--when slicing from one version to the next.No, tweak.sh only works on your current filesystem, which is presumably already hacked. I'm suggesting that you mount your alternate partition, and check for an author file, etc. The Slicer should echo each file/directory that's being copied, so that will give you some indication that hacks are being copied over.

[MurrayW]

No, tweak.sh only works on your current filesystem, which is presumably already hacked. I'm suggesting that you mount your alternate partition, and check for an author file, etc. The Slicer should echo each file/directory that's being copied, so that will give you some indication that hacks are being copied over.Russ, I have been slicing, re-zippering, running tweak_uninstall.sh then tweak.sh. Is there any reason for me to re-zipper after slicing? Do I need to run tweak_uninstall.sh after slicing then rerun tweak.sh? In short, which (if any) of the following scenarios is necessary for an already zippered/hacked DirecTiVo running 3.1.5.f?

Option 1:
Run slicer to go from 3.1.5.f to 6.3.x
Run tweak_uninstall.sh
FTP latest tweak.sh to DirecTiVo
Run tweak.sh
Manually run some of the commands (30 sec skip, etc.) that are not handled by tweak.sh on 6.3.x

Option 2:
Run slicer to go from 3.1.5.f to 6.3.x
FTP latest tweak.sh to DirecTiVo
Run tweak.sh
Manually run some of the commands (30 sec skip, etc.) that are not handled by tweak.sh on 6.3.x

Option 3:
Run slicer to go from 3.1.5.f to 6.3.x
Pull drive and run zipper ver 2.8
Re-install drive
Run tweak_uninstall.sh
Run tweak.sh
Manually run some of the commands (30 sec skip, etc.) that are not handled by tweak.sh on 6.3.x

Option 4:
Run slicer to go from 3.1.5.f to 6.3.x
Pull drive and run zipper ver 2.8
Re-install drive
Run tweak.sh
Manually run some of the commands (30 sec skip, etc.) that are not handled by tweak.sh on 6.3.x


thanks,
Murray

[Cure]

Lord Vader (and others) -

You should go for it! Ran the slicer, rebooted. Ran tweak.sh over the network. Patched tivoapp. Completely painless. Skipped right over 6.3b and now we have the new Zipper as a safety net.

Thanks, Russ.

[MurrayW]

Lord Vader (and others) -

You should go for it! Ran the slicer, rebooted. Ran tweak.sh over the network. Patched tivoapp. Completely painless. Skipped right over 6.3b and now we have the new Zipper as a safety net.

Thanks, Russ.Cure, so you basically did what I outlined in my Option 2 just above your original post, correct? Do you have a 1 drive or 2 drive system?
thanks,
Murray

[Cure]

... you basically did what I outlined in my Option 2 just above your original post, correct? Do you have a 1 drive or 2 drive system?


Pretty much, except I'd gone up to 6.3a a while back. If you can telnet, you don't need to pull the drive.

1 drive. Good luck.

[MurrayW]

Pretty much, except I'd gone up to 6.3a a while back. If you can telnet, you don't need to pull the drive.

1 drive. Good luck.About the ONLY problem I have not had in trying to slice and hack my HR10-250's is telnet access!
thanks,
Murray

[rbautch]

Russ, I have been slicing, re-zippering, running tweak_uninstall.sh then tweak.sh. Is there any reason for me to re-zipper after slicing? Do I need to run tweak_uninstall.sh after slicing then rerun tweak.sh? In short, which (if any) of the following scenarios is necessary for an already zippered/hacked DirecTiVo running 3.1.5.f?No need to run the Zipper, ftp a new tweak.sh, or apply manual tivoapp patches. Just run the slicer, reboot, then run tweak.sh.

[Lord Vader]

Assuming, of course, one still has telnet or serial bash. If both are gone, one can't run tweak.sh.

That was my problem when trying to go from 6.3a to 6.3b.

[MurrayW]

No need to run the Zipper, ftp a new tweak.sh, or apply manual tivoapp patches. Just run the slicer, reboot, then run tweak.sh.So Russ, do you think that my problems might be due to running tweak_uninstall.sh after slicing, re-zippering (which is not needed, but shouldn't hurt correct?)? Is there something that tweak_uninstall.sh does if it is run on a freshly zippered drive (without running tweak.sh yet) that prevents tweak.sh from running correctly?
Sorry to be such a pest. I am going to try to re-zipper my drive and see if I can run tweak.sh on the freshly zippered drive.

thanks,
Murray

[MurrayW]

I am going to try to re-zipper my drive and see if I can run tweak.sh on the freshly zippered drive.

thanks,
MurrayNo go. Same problems where tweak.sh just hangs forever. I also had errors trying to use the slicer to go from 6.3b to 6.3c.

I was able to do the following manual patches and all looked like it went as it was supposed to. I tested the 30 sec skip before and after and it did start working after I applied these patches.

cp /tvbin/tivoapp /tvbin/tivoapp.orig
cd /tvbin

mv tivoapp tivoapp.tmp
cp tivoapp.tmp tivoapp
chmod 755 tivoapp


#No encryption
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=1602412


#30-second skip
echo -ne "\x10\x40\x00\x2b" | dd conv=notrunc of=tivoapp bs=1 seek=6713220


#Backdoors
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=2804900


#HMO/HME
echo -ne "\x34\x11\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=903436
echo -ne "\x24\x10\x00\x01" | dd conv=notrunc of=tivoapp bs=1 seek=1118524
echo -ne "\x10\x00\x00\x14" | dd conv=notrunc of=tivoapp bs=1 seek=5724672


mount -o remount,ro /
reboot


#(after reboot, clean up)
cd /tvbin
rm tivoapp.tmp

So I am still perplexed about this whole process and don't understand why tweak.sh does not work. Could it be some corrupt or missing file that tweak.sh is trying to access during one of the first steps of the script?

thanks,
Murray

[Cure]

No go. Same problems where tweak.sh just hangs forever.

Are you sure you're FTP'ing in binary mode?

[MurrayW]

Are you sure you're FTP'ing in binary mode?I'll check when I get home tonight. I know that I have set it to binary before and I think was able to set that as the default mode...but to be honest, I haven't checked lately, so this is definitely something to look into. I hope that is what it is.

Thanks for the suggestion.
Murray

[Bobblob]

I had some problems on the first go-round with Slicer going from 6.3b to 6.3c that left my tivo unbootable, so I yanked the drive, reimaged it with Zipper (6.3b), let the slices download again overnight, and this time I got it working. However, I found what had caused my problem in the first place.

The image Zipper created, using the recommended method ($5 LBA48 image, InstantCake 6.3b image, etc.) created an image that didn't include a /install directory in the root. Even though /install is empty, Slicer fails during the installSw.itcl portion if that directory doesn't exist.

After creating that directory manually, Slicer worked fine. Of course, I forgot to copy my backported USB drivers over, so after rebooting I only had a serial shell. Then I had to figure out how to put the backported drivers back on. (As everyone is so fond of saying around here, teach a man to fish... :-)) With the USB drivers back in, telnet was back, and then I was able to re-Tweak.Sh and get my various hacks back where I wanted 'em.

A few points about the script:
1) The TivoNCID version being installed is a few revisions older than the latest. Not sure if it matters much.
2) The /busybox created by The Zipper contains a ps that causes a segmentation fault on the HR10-250. The version in AlphaWolf's All In One tools (installed separately) doesn't show any useful info, for some reason, it just says that the supported parameters are "w". But it doesn't show any process info. Thankfully, the version in /ptvupgrade/busybox does work, though.
3) Given the issues with TivoWebPlus 1.3 on the HR10-250, I opted to remove the one it installs and go to a stock TWP 2.0 recent build.

Everything else that script does is fantastic, though. Joe is so much nicer than vi. :-)

[sk33t3r]

I am curious of there is any way to run mfsadd from a telnet session or do I have to remove the drives AGAIN???? when I ran zipper a few weeks ago, it didint run mfsadd or even ask about how mant drives.

Rbautch maybe this is something that can be add to the script!!!

[ckgoodwin]

Hey All,

I used slicer to go from 6.3a to 6.3c on my PTV hacked machine and overall it's working fine and all my hacks seem to have made it across except for some weird CRON behavior.

I have to admit up front that I am pretty much of UNIX and CRON newbie but here is what I have found:

- My CRON jobs weren't executing per the schedule in the crontab so I checked (via PS) from the bash prompt to the see if the CROND process was running and it was not.

- I used the Hackman interface to try and re-start CRON - it reported success, but when returning to the Hackman screen the start button was still green and said "Start" instead of "Stop" as it usually does once a process has been started - checking from bash again shows that CROD is not running.

- Every time I try and start CRON from Hackman, cronlog shows entries indicating that the jobs in CRONTAB (fakecall and clearing logs) executed immediately instead of at the specified time. I can hit the "start" button 5 times in 5 minutes and will get 5 entries in the cronlog.

- I can start CROND from bash and it seems to run ok, and is then shown as started within Hackman but when I close the telnet session it seems to exit.

Again, I am nube here so maybe I am missing something obvious so any suggestions are much appreciated...

- Chris

[rbautch]

Slicer fails during the installSw.itcl portion if that directory doesn't exist.The slicer should create the /install directory if it's not there. Also, InstallSW.itcl does not depend on that directory, and the slicer only uses it after (and if) InstallSW.itcl is run successfully. I don't discount your observation, but was there any output or error that led to conclude the /install directory was the culprit?
A few points about the script:
1) The TivoNCID version being installed is a few revisions older than the latest. Not sure if it matters much.
2) The /busybox created by The Zipper contains a ps that causes a segmentation fault on the HR10-250. The version in AlphaWolf's All In One tools (installed separately) doesn't show any useful info, for some reason, it just says that the supported parameters are "w". But it doesn't show any process info. Thankfully, the version in /ptvupgrade/busybox does work, though.NCID has been updated in the latest enhancement script and Zipper. Also, grab the latest version of busybox from my sig, which includes a full featured version of ps that works with 6.3. This has also been incorporated into the latest zipper.

[aprest]

Hey All,

I used slicer to go from 6.3a to 6.3c on my PTV hacked machine and overall it's working fine and all my hacks seem to have made it across except for some weird CRON behavior.

I have to admit up front that I am pretty much of UNIX and CRON newbie but here is what I have found:

- My CRON jobs weren't executing per the schedule in the crontab so I checked (via PS) from the bash prompt to the see if the CROND process was running and it was not.

- I used the Hackman interface to try and re-start CRON - it reported success, but when returning to the Hackman screen the start button was still green and said "Start" instead of "Stop" as it usually does once a process has been started - checking from bash again shows that CROD is not running.

- Every time I try and start CRON from Hackman, cronlog shows entries indicating that the jobs in CRONTAB (fakecall and clearing logs) executed immediately instead of at the specified time. I can hit the "start" button 5 times in 5 minutes and will get 5 entries in the cronlog.

- I can start CROND from bash and it seems to run ok, and is then shown as started within Hackman but when I close the telnet session it seems to exit.

Again, I am nube here so maybe I am missing something obvious so any suggestions are much appreciated...

- Chris


See my post #9680 in the " Hacking your Series 2 DTivo just got a WHOLE lot easier" thread for what I did to get crond running. I have had to do this after using Zipper 2.8, slicing or re-Zippering.

[MurrayW]

Are you sure you're FTP'ing in binary mode?I was ftp'ing in the "auto" mode. I switched it to binary and made that the default. I ftp'd the slicer and tweak.sh and tried running each of those and got the same errors as before -- tweak.sh hangs with no responses and slicer gives some errors (I posted them in another post). My rc.sysinit.author file is much shorter than the rc.sysint.author.orig file in the same directory. Do either one of this look normal?
rc.sysinit.author #!/bin/bash
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10
tnlited 23 /bin/bash -login &
tivoftpd
fakecall.tcl
route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0
/bin/bash </dev/ttyS2&> /dev/ttyS2&
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.1.223 192.168.1.1
mount -o remount,ro /
reboot
fi
fi


rc.sysinit.author.orig #!/bin/bash
# Zipper author file
echo "starting rc.sysinit.author"

echo "set environmental variables"
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox:/enhancements
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10

echo "starting telnet and ftp"
tnlited 23 /bin/bash -login &
tivoftpd

echo "starting serial bash"
/bin/bash </dev/ttyS2&> /dev/ttyS2&

echo "running fakecall"
fakecall.tcl
route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0

insmod /lib/modules/usbcore.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o
sleep 60
ifconfig eth0 192.168.1.218 netmask 255.255.255.0
route add default gw 192.168.1.1
echo
if [ -e /reboot_flag ]; then
mount -o remount,rw /
if rm /reboot_flag; then
reboot
fi
fi

######################################
mount -o remount,rw / &>/dev/null
rm /zipper_flag &>/dev/null
mount -o remount,ro / &>/dev/null

#############################################
# starting netserver to receive netperf requests
/busybox/netserver

#############################################
# starting NCID CallerID
touch /var/log/cidcall.log &
cd /var/hack/sbin; ./ncidd
cd /var/hack/bin; ./tivocid &

#############################################
# starting EndPadPlus
tivosh /enhancements/endpadplus.tcl 2 3 -seq -auto >> /dev/null &

#############################################
# starting Tivowebplus
/enhancements/TWPrun.sh

#############################################
# start crond after waiting 30 seconds
sleep 30
/busybox/crond

#############################################
# Check if var got wiped, and if so, rebuild symlinks from /enhancements/varhacks
if [ ! -e /var/vardelete_flag ]; then
sh /enhancements/var-symlinks.sh
fi
## Slicer - run network script only once.
if [ -e /slicer_firstboot ]; then
mount -o remount,rw /
if rm -rf /slicer_firstboot; then
tivosh /hacks/network.tcl 192.168.1.218 192.168.1.1
mount -o remount,ro /
sleep 30
sync
reboot
fi
fi

[aprest]

I was ftp'ing in the "auto" mode. I switched it to binary and made that the default. I ftp'd the slicer and tweak.sh and tried running each of those and got the same errors as before -- tweak.sh hangs with no responses and slicer gives some errors (I posted them in another post). My rc.sysinit.author file is much shorter than the rc.sysint.author.orig file in the same directory. Do either one of this look normal?
rc.sysinit.author #!/bin/bash
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10
tnlited 23 /bin/bash -login &
tivoftpd
fakecall.tcl
route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0
/bin/bash </dev/ttyS2&> /dev/ttyS2&
echo
if [ -e /firstboot_flag ]; then
mount -o remount,rw /
if rm -rf /firstboot_flag; then
tivosh /hacks/network.tcl 192.168.1.223 192.168.1.1
mount -o remount,ro /
reboot
fi
fi


rc.sysinit.author.orig #!/bin/bash
# Zipper author file
echo "starting rc.sysinit.author"

echo "set environmental variables"
export PATH=./:.:/utils:/bin:/sbin:/tvbin:/tivobin:/busybox:/enhancements
export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10

echo "starting telnet and ftp"
tnlited 23 /bin/bash -login &
tivoftpd

echo "starting serial bash"
/bin/bash </dev/ttyS2&> /dev/ttyS2&

echo "running fakecall"
fakecall.tcl
route add -host 204.176.49.2 gw 127.0.0.1
route add -net 204.176.49.0 gw 127.0.0.1 netmask 255.255.255.0

insmod /lib/modules/usbcore.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o
sleep 60
ifconfig eth0 192.168.1.218 netmask 255.255.255.0
route add default gw 192.168.1.1
echo
if [ -e /reboot_flag ]; then
mount -o remount,rw /
if rm /reboot_flag; then
reboot
fi
fi

######################################
mount -o remount,rw / &>/dev/null
rm /zipper_flag &>/dev/null
mount -o remount,ro / &>/dev/null

#############################################
# starting netserver to receive netperf requests
/busybox/netserver

#############################################
# starting NCID CallerID
touch /var/log/cidcall.log &
cd /var/hack/sbin; ./ncidd
cd /var/hack/bin; ./tivocid &

#############################################
# starting EndPadPlus
tivosh /enhancements/endpadplus.tcl 2 3 -seq -auto >> /dev/null &

#############################################
# starting Tivowebplus
/enhancements/TWPrun.sh

#############################################
# start crond after waiting 30 seconds
sleep 30
/busybox/crond

#############################################
# Check if var got wiped, and if so, rebuild symlinks from /enhancements/varhacks
if [ ! -e /var/vardelete_flag ]; then
sh /enhancements/var-symlinks.sh
fi
## Slicer - run network script only once.
if [ -e /slicer_firstboot ]; then
mount -o remount,rw /
if rm -rf /slicer_firstboot; then
tivosh /hacks/network.tcl 192.168.1.218 192.168.1.1
mount -o remount,ro /
sleep 30
sync
reboot
fi
fi

The second one looks like mine that works fine. The first one is incorrect.

[MurrayW]

The second one looks like mine that works fine. The first one is incorrect.I tried making a copy of rc.sysinit.author, deleting it and then renaming rc.sysinit.author.orig to rc.sysinit.author. After doing this, I tried running slicer and tweak.sh again and had the same problems. I did not reboot between copying and renaming. Would a reboot be in order before the new rc.sysinit.author would kick in?
thanks,
Murray

[Finnstang]

The author file is run during the startup sequence, so if you do not reboot after the copy/renaming, the renamed one will not be in effect.

[MurrayW]

The author file is run during the startup sequence, so if you do not reboot after the copy/renaming, the renamed one will not be in effect.Thanks....I guess if it hadn't be so late last night when I was doing this, I wouldn't have minded waiting for the rebooting process. I'll give it a try tonight.
thanks, Murray

[Bobblob]

Thanks Richard - on the whole /install directory thing, the results I had went like this:
- I built the machine as previously described (Zipper, InstantCake 6.3b image, etc.)
- I ran the slicer to upgrade to 6.3c. It said something about not being able to create the new SW partitions, failing during the "installing new software" phase, and suggested running installSw.itcl manually to see where the failure was. The command that failed definitely referenced /install. But it didn't create this directory automatically.
- Strangely, installSw.itcl when run manually completed normally and flipped the bootpage.
- I flipped it back, messed around a bit more. but ultimately screwed something up and after rebooting it was in an unbootable grey-screen-of-death.
- I reimaged as in step 1, ran add63 and waited overnight for the slices to come down again.
- I started the slicer again, just as before, got the same error. This time I created /install manually, ran the slicer again, and boom, problem solved. :-)

I'm hoping I don't have to reimage again in the future (your skills are growing, young Padawan...), but if I do, I'll update my Zipper image first. Thanks for such an awesome script and tool!

[ctromp]

I have a USB200M v.1 and 3.1.5f. Everything is working fine. However, all this talk about DST has me a bit worried so I am considering going to 6.3c. I do have teh 6.3 slices in MFS. My understanding is that I should be able to download the slicer from PTVUpgrade and just run it without having to do anything else to get to 6.3c. True?

Thanks

[rbautch]

I have a USB200M v.1 and 3.1.5f. Everything is working fine. However, all this talk about DST has me a bit worried so I am considering going to 6.3c. I do have teh 6.3 slices in MFS. My understanding is that I should be able to download the slicer from PTVUpgrade and just run it without having to do anything else to get to 6.3c. True?

ThanksTrue.

[Bobblob]

Slicer should do the job for you just fine, yes. Things to keep in mind:
1) Watch closely when it copies your hack directories. If it missed any, ctrl-C out of the slicer after that step, and move the rest manually to the new partition, which you'll find mounted under /install.
2) If you have the v1 USB200M, I don't think you need backported USB drivers and it should just work. I have the v2, which required more work. But if you are using backported drivers for some reason, the slicer doesn't handle those for you and you'd need to copy those over manually as well prior to rebooting.
3) I stroooongly recommend having a serial cable nearby in case you lose your telnet access for some reason. (I did, but based on your config you probably won't.)

[rbautch]

The command that failed definitely referenced /install. But it didn't create this directory automatically.Interesting. Do you know what the exact error was? If not, and you have the stomach to recreate the error, it might help others.

[rbautch]

I was ftp'ing in the "auto" mode. I switched it to binary and made that the default. I ftp'd the slicer and tweak.sh and tried running each of those and got the same errors as before -- tweak.sh hangs with no responses and slicer gives some errors (I posted them in another post). My rc.sysinit.author file is much shorter than the rc.sysint.author.orig file in the same directory. Do either one of this look normal?They both look normal. The first one is normal for a 6.2/6.3 installation, i.e. network params are set in MFS. The second one is appropriate for 3.1.5f or other 3.x software, i.e. network params are set in the author file and drivers are also insmodded here too.

[Smuuth]

I stroooongly recommend having a serial cable nearby in case you lose your telnet access for some reason. (I did, but based on your config you probably won't.)I have used PTVNetHD and InstantCake to put my HR10-250 back to 3.1.5f after having problems with 6.3a. I also added capacity and networking and am generally pretty happy. I now have the 6.3c slices on my unit and was considering giving the slicer a shot, knowing that I now can go back to 3.1.5f if I am unhappy with 6.3c.

My question is regarding your comment and the instructions for Slicer regarding the serial cable.

"1. IMPORTANT - we strongly recommend the use of a serial cable when using The Slicer. Due to the differences in OS versions, USB drivers, DHCP and STATIC IP settings, you still may lose USB Ethernet connectivity when using The Slicer, so a serial connection (bash access) is very important to have. "

I am at a loss to figure out how to use a serial cable to connect to my HR10-250 when there is no DB-9 connector on the unit. Can you explain where I connect the serial cable to the HR10-250? Thanks

[PJO1966]

I have used PTVNetHD and InstantCake to put my HR10-250 back to 3.1.5f after having problems with 6.3a. I also added capacity and networking and am generally pretty happy. I now have the 6.3c slices on my unit and was considering giving the slicer a shot, knowing that I now can go back to 3.1.5f if I am unhappy with 6.3c.

My question is regarding your comment and the instructions for Slicer regarding the serial cable.

"1. IMPORTANT - we strongly recommend the use of a serial cable when using The Slicer. Due to the differences in OS versions, USB drivers, DHCP and STATIC IP settings, you still may lose USB Ethernet connectivity when using The Slicer, so a serial connection (bash access) is very important to have. "

I am at a loss to figure out how to use a serial cable to connect to my HR10-250 when there is no DB-9 connector on the unit. Can you explain where I connect the serial cable to the HR10-250? Thanks

There is a jack in the back marked "serial". Weaknees has the cable for sale on their website (http://www.weaknees.com/tivo-cables.php). It's the last item under Standard TiVo Replacement Cables.

[MurrayW]

They both look normal. The first one is normal for a 6.2/6.3 installation, i.e. network params are set in MFS. The second one is appropriate for 3.1.5f or other 3.x software, i.e. network params are set in the author file and drivers are also insmodded here too.So I guess trying to use my .orig file with my current 6.2 would not be a good idea. So any ideas on what I should next try to get tweak.sh and/or the slicer to run? Is there anyway to run tweak.sh in some sort of "logging" mode so I can see what it is doing and where in the script it hangs?
thanks,
Murray

[Smuuth]

There is a jack in the back marked "serial". Weaknees has the cable for sale on their website (http://www.weaknees.com/tivo-cables.php). It's the last item under Standard TiVo Replacement Cables.Thanks for that. I saw the port marked "serial" but had never seen a serial cable with a mini-jack type connector. I appreciate the information.

[PJO1966]

Thanks for that. I saw the port marked "serial" but had never seen a serial cable with a mini-jack type connector. I appreciate the information.


No problem. I'm just glad I could finally answer a question in this thread.

[dswallow]

Thanks for that. I saw the port marked "serial" but had never seen a serial cable with a mini-jack type connector. I appreciate the information.
Oddly enough, I already had two -- one for my Home Theater Master remote controls and one for a bar code scanner I use with some DVD/Book inventory programs. I noticed that AFTER I made a serial cable to use with the TiVo's. So now I have 3. :)