superpatch-67all - (Support)

[NutKase]

[EDIT] PEOPLE! STOP POSTING NEWBIE QUESTIONS IN THE SUPERPATCH-67ALL SUPPORT THREAD. If you don't know how to run a .tcl script, start a thread in the NEWBIE FORUM and ask about your problem there. Just because you found out something you didn't know when trying superpatch-67all doesn't make it a superpatch-67all support requirement. 7-10-05

-------------------------------------------------------------------------
Superpatch-67all - (for all known 6.x and 7.1x versions)

Here's where to ask your questions. Do not post questions in the release thread.

The release, and instructions on it's use, are posted in the Superpatch-67all file release thread. (http://www.dealdatabase.com/forum/showthread.php?t=43325)

I won't respond to support requests in the files forum. Please post here.

Also, there's lots of information in the associated .txt file.


NOW LET'S SET SOME GROUND RULES
Using an advanced patch to change major portions of the central runtime file on your tivo is a MAJOR undertaking. If you don't know what you're doing DON'T DO IT. At some point we have to assume that "If it was easy, everybody would be doing it."

DON'T LET THIS THREAD DEGENERATE INTO A RECAP OF THE PROBLEMS COVERED IN THE Superpatch-4all - (Support) (http://www.dealdatabase.com/forum/showthread.php?t=37197)thread.

I'm not a moderator but, if I were I'd delete ANY and ALL questions relating, but not limited, to:

Errors like:
'no such file or directory'
'I've just hacked my tivo and I can't run any .tcl files'
'FSAllocate problems'
'array: command not found'

Questions like:
'I don't have a virgin tivoapp, how can I fix it back?'
'Someone else hacked my tivo for me, how can I fix it back?'
'My dtivo keeps forgetting it's name and MRV won't work, what do I do?'
EDIT - More OT questions added
'Can someone give me a reason not to let my tivo phone home?'
'How do I remove the 30-second skip patch?'
'Is "superpatch-67all" compatible with a p t v ugraded Samsung Sir4040 with a new 160gb drive?'
'When I execute superpatch-67all, using bash [(instead of the command in bold in the release thread)] this is what I get:
- bash-2.02# bash superpatch-67all-NutKase-1.0.tcl
- superpatch-67all-NutKase-1.0.tcl: array: command not found


I'm sure that list should be longer but I'll stop. The point is that I haven't released this file because I care about your tivo and how it works. I wouldn't keep my tivos if I couldn't MRV with unencrypted video recordings and I don't think anyone else should have to either. The work was needed and I and several others did it. It's just an easy way for us to share our work with each other and others like us and avoid finding and typing a bunch of patches manually.

Now if every downloader will do their part and READ the release thread, this thread, background links, and the board in general, I'd appreciate it.

Let's don't re-ask and re-answer the questions in the Superpatch-4all - (Support) (http://www.dealdatabase.com/forum/showthread.php?t=37197) thread.

[EDIT]
In order to provide the link above I reread the last 3 posts in the 'Superpatch-4all Support' thread = Quite comical!


NutKase

[NutKase]

Reserved 1

[JackBlack]

Works fine on my DVR80 running 6.2. Being in a 72.5 market kept me from going the 4.x route. Thanks for the fine work.

[AlphaWolf]

KNOWN ISSUES
6.x
6.1 (R10) tivoapps are not supported. May be supported in a future release.

FWIW, I *think* that 6.2 will run fine on a prom modded R10 so long as you use a kernel that supports it. There shouldn't be any special hacks required that I can tell.


Network settings screen not accessible. May be supported in a future release.
'Search by Title (Demo)' menu item under PickPrograms. May be removed in a future release.

It might be better to not patch the spigot abroad, but to force open the individual components that are necessary to enable MRV, thus you'll have the network config screen and you wont have the trial nags. Course somebody would need to find those patches first.

[dewalt]

Tried the patch out, and this is what I found...

-Intermittently found the tivo desktop server for photos and music. But when it did, they worked fine.

-The Tivo desktop could not find the tivo...basic network setup (same subnet, etc)

-The standby option on the main menu is now on the messages and setup menu. I'm assuming this is because the Music & Photos took its place.


I ended up undoing it.

[jeboo]

Tried the patch out, and this is what I found...

-Intermittently found the tivo desktop server for photos and music. But when it did, they worked fine.

-The Tivo desktop could not find the tivo...basic network setup (same subnet, etc)

-The standby option on the main menu is now on the messages and setup menu. I'm assuming this is because the Music & Photos took its place.


1. Sounds like dhclient is still running...Are you losing network connectivity too?

2. Tivo Desktop will not work with 6.x for transferring recordings.

3. Small price to pay I'd say...Who uses standby anyway :)

jeboo

[dewalt]

1. Sounds like dhclient is still running...Are you losing network connectivity too?

2. Tivo Desktop will not work with 6.x for transferring recordings.

3. Small price to pay I'd say...Who uses standby anyway :)

jeboo

Thanks for the response. Dhclient is definitely not running. I've used the tivo for streaming shows, transferring using tytools, etc.

I'm not going to worry about it - I only have one tivo so MRV wont be of any use to me. I assumed tivo desktop would transfer shows, but it's all good - still have tytools :)

[nova1]

any other ideas or logs I can post

What does /var/log/tvlog say regarding the LinuxNetworkInterface If0: configuration? Does it say Automatic config or Manual config?

[NutKase]

However, the 4.0.1b dtivo running superpatch 4.0 and setting mrv name to tivo1 has no entry for the new tivo3 running 6.2 (which was just updated with this patch.).

1. There's no superpatch named 'superpatch 4.0'. What EXACTLY did you run?
2. Is there a tivo2?

I even reran set_mrv_name after rebooting the first time and rebooted again.

There are several versions of set_mrv_name. Which did you run?

(I) re-ran set_mrv on both still no go..

Again, if you can't accurately type what you did you won't get help. What is 'set_mrv'? You're being lazy and people ignore your post because by what you typed it'll be a long and drawn out process just to figure out what you're actually doing, much less help you.

The only other thing I reran on the 6.2 box is the bufferhack after superpath 67 to incrase the buffer size....

Incrase? Superpath? Superpath 67?

What's that? See what I mean? The proper name of this patch is superpatch-67all at a minimum.

Thanks for all your hard work and releasing this patch.. has anyone else had success with this patch in getting mrv to work?

Yes, or it wouldn't have been released. Note, I fixed all your CAPS for you.


Now, here's what I'd do.

1. Make absolutely sure that you have superpatch-4all applied to the 4.0.1b dtivo. Including READING THE MESSAGES output by the file during application.
2. Make absolutely sure that you have superpatch-67all applied to the 6.2x dtivo. Including READING THE MESSAGES output by the file during application.
3. After seeing 'Success!' on each, apply the set_mrv_name_67.tcl included with this release to both dtivos and specify a different name for each.
4. Reboot both dtivos and report any errors and their status.

Now, if you screw up your machines because you forget to chmod tivoapp when putting a virgin one back on your tivo to patch don't post about it here.

[EDIT] In case anyone is wondering, lgkahn removed his 'useless' and 'error ridden' post and, I HOPE by mistake, some MOD deleted it.

That said, I'm leaving my corrections as is. I stand by them and they were necessary.


NutKase

[LanMan]

Jeboo,

Thanks for the post to dewalt about dhclient. I had renamed dhclient and
used ifconfig for a static ip in my rc.sysinit.author. Been working fine
with no problems. Applied superpatch-67all and named my dtivo with
set_mrv_name_67.tcl. Had the same symptoms as dewalt.

I renamed dhclient back, got rid of the ifconfig statements in rc.sysinit.author
and mrv works great with another Dtivo running 4.01b!

Now to figure out why not using dhclient and using ifconfig would cause problems. I'll post when I find it.

Thanks NutKase and the rest for all the hard work!

Eric

[dot19408]

I ran superpatch-67all-NutKase-1.0.tcl and set_mrv_name_67.tcl and every thing went good.

(none):/var/hack/patch$ ./superpatch-67all-NutKase-1.0.tcl

superpatch-67all-NutKase-1.0.tcl
(C) 05/08/2005 by NutKase, et al - COMMERCIAL USE PROHIBITED

Credit goes to CapablePerson66, rc3105, and others who wish to
remain anonymous. We thank ESPECIALLY alldeadhomiez for his time and knowledge.

All errors are the fault of Anonymous :-) .

Your TiVo Software version is 6.2-01-2-321
Please write down your TiVo Software version.


Checking your tivoapp patch locations...

Patching your tivoapp...

Success!
________
1. Your 6.2-01-2-321 tivoapp was updated with the proper superpatch-67all
2. Your original tivoapp was backed up and is called /tvbin/tivoapp.original.
3. You'll need to run the set_mrv_name_67.tcl, I've included, to 'name' your tiv
o.
(none):/var/hack/patch$ ./set_mrv_name_67.tcl Our_TiVo
Setting nametable for "Our_TiVo"...
Reboot your tivo for the changes to take effect.
(none):/var/hack/patch$
(none):/var/hack/patch$ reboot

However, I set it to record 3 shows today, and nothing is in the Now Showing list.

I got home and recorded Stargate SG-1, while it was recording it showed up in the Now Showing list and showed the red recording dot. As soon as it was done recording the Now Showing list was blank.

The list is BLANK not "Empty" I can scroll endlessly up or down screen after screen with NO DATA in the list. If I perss "select" I get the BOOMP, so there is nothing in each slot.

If I rename tivoapp and copy the original back (reboot), record a show, it showsup in the list and there are no "blank" slots in the list.

Thanks,
dot19408

[LanMan]

dot19408,

Had the same "BLANK not "Empty" Now Showing. After 1 -2 minutes the list showed up.

I think the Dtivo is searching your LAN for another Dtivo for mrv capability, at least it was in my case. Once I changed my Dtivo to use dhcp, it found the other Dtivo and works properly.

Still don't know why it didn't like the ifconfig and static IP.

Eric

EDIT DNS solved it. Never had DNS set on my two Dtivo with 4.01b software. Thanks

[7.1]

dot19408,

Had the same "BLANK not "Empty" Now Showing. After 1 -2 minutes the list showed up.

I think the Dtivo is searching your LAN for another Dtivo for mrv capability, at least it was in my case. Once I changed my Dtivo to use dhcp, it found the other Dtivo and works properly.

Still don't know why it didn't like the ifconfig and static IP.This is a well known issue when you have a misconfigured DNS server. It really has nothing to do with the superpatch, but if you search for "superpatch" and "DNS", you'll get a lot of hits. Here's (http://www.dealdatabase.com/forum/showthread.php?t=38452&highlight=superpatch+DNS) one.

[jasch]

Hmmm. Well I applied Superpatch67 to my 6.2 units, with mixed results.

I removed the first two lines of the patch, since I have no use for 30SS or Backdoors. Then applied the patch on original tivoapp's. I set the mrv names on each one, and rebooted.

I have the music and photos option, but I don't have the other tivo's folder on Now Playing (which I did on 4.x after applying the previous superpatch available for that version).

I still have network connectivity on both units (only IP, no Gateways set. I've had it like that for months, to avoid the units being able to get "out" to the Internet). I know I need a "gateway" for Music and Photos to work properly (unless it's a local IP I am trying to get).

Anyway, I could care less about HMO, I am trying to get MRV working.

Any ideas why the units don't see each other? I guess it has to do with using a fixed IP insead of DHCP. Which command do I use to set up the DNS? (funny thing is that on 4.x it worked with a fixed ip)

Thanks

BTW, way to go NutKase.

[ZaTHRaS]

Hughes DTIVO SD-DVR40 up'd to 120
Philips DTIVO DSR704 up'd to 80
Both have:
6.2 forced upgrade from sat dl/edit script
killhdinitrd, Backdoors enabled
tivotools, mfs_ftp, TWP, "No encrypt" patch
Linksys usb200m loaded using backport drivers.(not forced in .author)
I have access, any method
Philips DTIVO DSR704 up'd to 80 3.1.1e waiting on "D" to upgrd to 6.2


I'm in with jasch.
Except the editing of the patch. Ran with success. (orig tivoapp)
I do have static ip and gw set.
#Set IP Address
ifconfig eth0 10.0.0.252 broadcast 10.0.0.255 netmask 255.255.255.0
route add default gw 10.0.0.254 netmask 0.0.0.0 metric 1
I am receiving Music/Photo, so I am contacting mothership.
Read over the superpatch4all thread in hopes of resolving without going DHCP which seemed to help many people.(never installed 4.x)

Added these DNS entries:
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
This did block access to tivo but to no resolution for mrv.

Blocking access from router now but, the today show is recording while the wife sleeps, can't reboot. :eek:

way to go NutKase

***** Moved Discussion to this thread here (http://www.dealdatabase.com/forum/showthread.php?t=43375) My reply to this post is #4 here (http://www.dealdatabase.com/forum/showpost.php?p=222445&postcount=4)

[dot19408]

This is a well known issue when you have a misconfigured DNS server. It really has nothing to do with the superpatch, but if you search for "superpatch" and "DNS", you'll get a lot of hits. Here's (http://www.dealdatabase.com/forum/showthread.php?t=38452&highlight=superpatch+DNS) one.

Thanks 7.1,

I did not see a way to "configure" DNS on the TiVo.
I'm a Linux noob, so this may be simple.

My router is the DNS relay for the house, but the TiVo is set up static and (I guess) is not finding the DNS...

Is there a line to add to ifconfig for DNS?
I've googled and have not found anything yet.

Thanks,
dot19408

[jasch]

By examining the dhcp-scripts, the DNS information is on /etc/resolv.conf

You need to have something like this:

search localdomain
nameserver x.x.x.x
nameserver x.x.x.x

Substitute x.x.x.x for the IP of your DNS.

The file seems to get zapped when your Tivo boots up, so you would need to find a way to protect it from being reset.

[7.1]

In the interests of keeping NutKase's support thread focused, I'd like to suggest we move network configuration discussions to a new thread. Maybe "Network configuration issues with HMO/MRV and superpatch-67all" in the Series 2 Support forum.

Superpatch-67all is working without issues for many. It's clear that we don't have a full understanding of why some people are having problems, but I still believe it's likely the result of network configuration issues. Let's take the long troubleshooting back and forth to another thread. We can summarize here if something useful comes out of it. I can suggest some troubleshooting approaches in a new thread.

[NutKase]

In the interests of keeping NutKase's support thread focused, I'd like to suggest we move network configuration discussions to a new thread.

I agree.


Maybe "Network configuration issues with HMO/MRV and superpatch-67all" in the Series 2 Support forum.

Should be 'ANY' superpatch.

Superpatch-67all is working without issues for many. It's clear that we don't have a full understanding of why some people are having problems, but I still believe it's likely the result of network configuration issues. Let's take the long troubleshooting back and forth to another thread. We can summarize here if something useful comes out of it. I can suggest some troubleshooting approaches in a new thread.

Yes the network configuration issues, that some users experience, were previously known as the 'Now Showing/Playing bug'. When end users start 'really' networking their tivos together we get these questions.

These issues are why I referred every downloader to the 'Superpatch-4all - (Support) thead'. I guess I need to add this to my list of 'problems already covered not to rehash' as mentioned above.

I'm positive that we'll find that the NP/NS issues are DNS or network setup related as you've already linked...

BUT, I'll update my Support/Release theads to reflect an easier path than 'redo' for the new/end users if we 'show them again'.

Thanks for your help.


NutKase

[Thinkdiff]

I upgraded 3 tivos last night from 4.0.1b-02 to 6.2, so they were pre-configured for proper networking and had the superpatch for 4.0.1b applied. I upgraded the first tivo, applied superpatch-67all, set the name and it immediately (after restart of course) found the BestBuy Music stuff, and my other 2 tivos running 4.01b still (and worked fine playing shows off them). So I went ahead and upgraded the other two, with the same results. Zero problems so far. Thanks a lot NutKase and everybody else that worked on it! Great stuff again

[k9cruiser]

The Superpatch array "patch_6_2" contains

0x00e3599c "0320f809 3c020000"

yet the NoCSO location documented in:

http://www.dealdatabase.com/forum/showpost.php?p=159809&postcount=8

says NoCSO is

Sw Version Offset Original Value New Value
6.2 00a3599c 0320f809 3C020000

So, is there a typo in the superpatch? (0x00e3599c should be 00a3599c ?) OR are the two patch locations reference above not related?

[7.1]

So, is there a typo in the superpatch? (0x00e3599c should be 00a3599c ?) OR are the two patch locations reference above not related?
Hum. They certainly look related. In fact 0x00e3599c - 0x00a3599c == 0x0040000. Why that's exactly the constant used to convert between VMA's and file offsets! reference (http://www.dealdatabase.com/forum/showthread.php?p=178198#post178198).

Do you suppose that's just an accidental coincidence? ;)

[NutKase]

The Superpatch array "patch_6_2" contains

0x00e3599c "0320f809 3c020000"

yet the NoCSO location documented in:

http://www.dealdatabase.com/forum/showpost.php?p=159809&postcount=8

says NoCSO is

Sw Version Offset Original Value New Value
6.2 00a3599c 0320f809 3C020000

So, is there a typo in the superpatch?

NO! 7.1 has graciously provided you with a link.

Let it be the last. We're not going to teach 'patch converting' or 'applying' in the superpatch-67all support thread.

This thread is for figuring out problems knowledgable people have in applying this patch... which should be very few and VERY NEW, since knowledgable people have already tested it.

Having folks wonder and ask about the patch contents/style belongs in a 'newbie' forum to keep this support thread SMALL.


NutKase

[7.1]

In the interests of keeping NutKase's support thread focused, I'd like to suggest we move network configuration discussions to a new thread. Maybe "Network configuration issues with HMO/MRV and superpatch-67all" in the Series 2 Support forum....
We can summarize here if something useful comes out of it.
...Here's the promised summary. Details can be found in this (http://www.dealdatabase.com/forum/showthread.php?t=43375) thread. Any follow up discussions and questions should go to that thread.

There are two two different network configuration problems that might affect superpatch users on 6.2:

The first one is a 'delayed' NowShowing list. This was also visible with the 4.x superpatch and seems to be the result of a slow timeout to a misconfigured DNS server. For dtivo's, ADH's suggestion is to use 0.0.0.0 for both the DNS server and the gateway. This should cause DNS lookups to fail fast. For SA tivos, just make sure your DNS server and gateway are valid and not blocked. This problem has been covered ad nauseam before. Search for "DNS" and "superpatch" and you'll get many hits.

The symptoms of the second issue are that the superpatched tivo's can't see each other in the MRV list. A superpatched 6.2 tivoapp doesn't provide access to the network settings user interface screens. If you configure your network manually in your rc.sysinit.local, the tivo software doesn't add it as a broadcast interface for MRV, so no broadcast packets get sent. Possible solutions: Let the TiVo use DHCP to configure the network. You can set static IP's for your tivo on your dhcp server. Setup networking using the TiVo UI on 4.x before upgrading to 6.2 via slices. This populates the required sections of MFS with network configuration data. Populate the required sections of MFS via a tcl script, such as the one lgkahn posted here (http://www.dealdatabase.com/forum/showthread.php?p=222557#post222557). Invoke /sbin/hotplug to inform the tivo software of the network interface after you set it up:ACTION=register INTERFACE=eth0 /sbin/hotplug net
1.-3. have been tested and have been verified to work. ADH suggested 4., but it hasn't been verified.

If broadcasts are correctly configured, you should see a message such as May 13 16:49:39 (none) KnownHost[17020]: Added TiVoConnect broadcast address 192.168.1.255
in your /var/log/tvlog.

[exiva]

i let my tivo upgrade because it was being a pain in the ass getting program guides (it kept telling me i had to reboot and wasnt getting them) so now i have 7.1b-01 will a superpatch for them be out soon?

never mind, i think i was confused by the first post in the superpatch-67all thread in the files section :o

[madlobster]

'Search by Title (Demo)' menu item under PickPrograms. May be removed in a future release.

What exactly is this? It doesn't do anything on my TiVo.

[mrblack51]

What exactly is this? It doesn't do anything on my TiVo.

because of the whole "tivo basic" and "tivo plus" thing on 5.x, there are certain menu items which are connected to the "tivo basic" mode. the menu item is simply an annoyance, thats all.

[AlphaWolf]

If you use the search by title (demo) option, it'll allow normal search by title, but then when you select the show it gives you a nag telling you that tivo plus will activate that feature. FWIW I have found a way to remove this particular menu entry, but its a bit messy.

[exiva]

has a way to remove the yellow star promotions from the TiVo Central been found yet for 7.x?

[kelsky]

I have three DVR40's all hacked to 6.2 and Superpatch67 working great! Awesome patch and great work!!! My fourth unit is a Pioneer 810h. It is unhacked but does have a lifetime subscription. The superpatch does not work with the 810 but it does see the 810 as well as the 810 sees the other units. But it will not transfer in either direction. Is there the possibility to hack the 810 to allow the transfers both ways? The current version is 5.x on it. I know that any general code to authorize it is wrong, but maybe there is a fix to allow legitimate users access to move back and forth recordings.

[7.1]

Is there the possibility to hack the 810 to allow the transfers both ways? The current version is 5.x on it. I know that any general code to authorize it is wrong, but maybe there is a fix to allow legitimate users access to move back and forth recordings.Your best bet is to wait for TiVo to release 7.x on the 810.

[mrblack51]

I have three DVR40's all hacked to 6.2 and Superpatch67 working great! Awesome patch and great work!!! My fourth unit is a Pioneer 810h. It is unhacked but does have a lifetime subscription. The superpatch does not work with the 810 but it does see the 810 as well as the 810 sees the other units. But it will not transfer in either direction. Is there the possibility to hack the 810 to allow the transfers both ways? The current version is 5.x on it. I know that any general code to authorize it is wrong, but maybe there is a fix to allow legitimate users access to move back and forth recordings.

ah, yes. this question was surely going to come up eventually. and, as 7.1 pointed out, your best bet is to wait. can it be done? sure. has it? nope. also remember that there are a variety of 5.x flavors running on different models (5.4.x on toshiba and humax burners, 5.1.x on toshiba players, 5.2.x on pioneer burners)

[Gunnyman]

just wanted to chime in and thank NutKase et al for the great work.
I took 2 DTivos from 4.01b to 6.2 with all the bells and whistles without difficulty.

[BillL]

I forced a connection to the DVR service in hopes of getting channel logos to show up (I imaged with the 6.2 small image). Now, in the System Information screens, under Spigot:MRV and Spigot:MUSICPHOTO, it now shows 180 days out as the expiration date of the certificates, where before it showed sometime in 1969. Does this mean that the HMO features will stop working in 180 days (Nov. 15 for my unit), or will the Superpatch allow them to continue despite the expiration of the certs? Or is this something we are not sure of yet due to changes in the software?

I have a feeling I should just redo the tivoapp patches to get rid of this, and learn my lesson about dialing in...

OTOH, it is interesting that the certificates were renewed upon calling in, considering that I should not have HMO/MRV in the first place...

Tim

DO NOT LET YOUR TIVO CALL HOME IF YOUR TIVO IS SUPERPATCHED.

[EvilJack]

I have the super patch installed and so far
things seem to be working. ( I onlt have one
Tivo set up with the HMO option right now )

One of the new menu Items I see is:
Music & Photos

I see that I can add a local server....
but that's about all I've figured out so far....
Does anyone know of a howto or thread or
something that will give a few details/hints
on how to get some of the new HMO features
working once you have them enabled?

jack

[AhoyMatey]

I have the super patch installed and so far
things seem to be working. ( I onlt have one
Tivo set up with the HMO option right now )

One of the new menu Items I see is:
Music & Photos

I see that I can add a local server....
but that's about all I've figured out so far....
Does anyone know of a howto or thread or
something that will give a few details/hints
on how to get some of the new HMO features
working once you have them enabled?

jackI don't know if this question is appropriate for this thread, but when MRV is enabled, you'll see other MRV enabled TiVos at the bottom of your Now Playing list. To see photos and music you need an HMO server running on a PC namely TiVo Desktop or JavaHMO.

[Archer]

DO NOT LET YOUR TIVO CALL HOME IF YOUR TIVO IS SUPERPATCHED.

Does this apply to DirecTivos as well? This is the first warning I've seen not to call in with a superpatched tivo.

Thanks,
Archer

[cheer]

Does this apply to DirecTivos as well? This is the first warning I've seen not to call in with a superpatched tivo.

Thanks,
Archer
It especially applies to DirecTivos. There's no reason to let them call home -- unlike SA Tivos, DTivos get guide info, etc., from the satellite. Yes, it's a slight inconvenience for pay-per-views, but as many others have pointed out, we don't want to draw attention to this stuff.

[lgkahn]

no blocking the dtivo from contacting tivo via the network has nothing to do with direct tv and ppv. you can still have a phone hooked up and they can still call tivo and you can still order ppv via the remote.. I have the tivo ips blocked in my firewll and a phone hooked up for caller id and my purchases still get to directtv and I can still order via the remote (

[cheer]

no blocking the dtivo from contacting tivo via the network has nothing to do with direct tv and ppv. you can still have a phone hooked up and they can still call tivo and you can still order ppv via the remote.. I have the tivo ips blocked in my firewll and a phone hooked up for caller id and my purchases still get to directtv and I can still order via the remote (
Fair enough. I pulled the phone lines from the boxes right after I hacked 'em.

[HuMan321]

I had a drive failure after the 6.2 upgrade and I restored the 62small.mfs on a new drive. I have the 3.1.1.5 kernal from PTV 4.1 enhanced boot CD and I have FTP and Telnet working.
I FTP'd both .tcl files from NutKases superpatch in the files section. They were FTP'd with filezilla to /var. I tivoshed them and received the below error.

I tried to chmod 755 them and the same error. I downloaded the latest file from DDB and overwrote and still have the error. I haven't a clue where to go now. The Tivo is working great with FTP and Telnet, but would sure like to patch with superpatch. Any response is appreciated.

When I ran tivosh superpatch-67all-NutKase-1.0.tcl from telnet I received the error of
initializeProgramOrDie (tivosh) failed: 0x11001

[fixn278]

I had a drive failure after the 6.2 upgrade and I restored the 62small.mfs on a new drive. I have the 3.1.1.5 kernal from PTV 4.1 enhanced boot CD and I have FTP and Telnet working.
I FTP'd both .tcl files from NutKases superpatch in the files section. They were FTP'd with filezilla to /var. I tivoshed them and received the below error.

I tried to chmod 755 them and the same error. I downloaded the latest file from DDB and overwrote and still have the error. I haven't a clue where to go now. The Tivo is working great with FTP and Telnet, but would sure like to patch with superpatch. Any response is appreciated.

When I ran tivosh superpatch-67all-NutKase-1.0.tcl from telnet I received the error of
initializeProgramOrDie (tivosh) failed: 0x11001

1) Did you transfer it in binary mode? If you aren't sure, redo it.
2) Can you run any tcl's?

[AlphaWolf]

no blocking the dtivo from contacting tivo via the network has nothing to do with direct tv and ppv. you can still have a phone hooked up and they can still call tivo and you can still order ppv via the remote.. I have the tivo ips blocked in my firewll and a phone hooked up for caller id and my purchases still get to directtv and I can still order via the remote (

Your firewall filter wont fix anything as long as your tivo is able to contact tivo via the phone line, and it can report anomalous MRV activity that way. I do believe that with the current 6.2 superpatch available, this is unavoidable without tweaking the tivos iptables.

[mateom199]

Your firewall filter wont fix anything as long as your tivo is able to contact tivo via the phone line, and it can report anomalous MRV activity that way. I do believe that with the current 6.2 superpatch available, this is unavoidable without tweaking the tivos iptables.

Sorry I'f I'm misunderstanding you, AW, but are you saying that even with some form of blocking the phone home via the net (firewall, route -add host method, etc) the tivo will phone home using the modem?

I hae my 6.2 DTivo hooked into the phoneline for caller id and PPV, but its set to make Tivo call over the net, which is blocked by my router. I haven't seen any instances of the failed net call resulting in a phone call....

But I might have misunderstood you.

[millercentral]

Here's a thought: Would adding a bogus "prefix" to the dial-in number be enough to block the call from succeeding? Does the DirecTV PPV dialin rely on the same prefix when it makes its call (I would doubt it, since it wouldn't use the network like ,#401 would suggest)?

[HuMan321]

1) Did you transfer it in binary mode? If you aren't sure, redo it.
2) Can you run any tcl's?

Thanks for the reply. I did transfer in binary, several different times in fact just to make sure. It seems I cannot run either of the tcl's in the superpatch. I downloaded it again and used winrar to unzip and transferred binary and keep getting the same errors
Here is some telnet paste
bash-2.02# superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001
bash-2.02# tivosh superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001
bash-2.02# chmod 755 superpatch-67all-NutKase-1.0.tcl
bash-2.02# superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001
bash-2.02# tivosh superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001

[zen_monk]

Thanks for the reply. I did transfer in binary, several different times in fact just to make sure. It seems I cannot run either of the tcl's in the superpatch. I downloaded it again and used winrar to unzip and transferred binary and keep getting the same errors
...

I vaguely recall that I have seen this when the .tcl files had been opened/saved in a DOS/WIN32 editor that didn't preserve the Unix style of CRLFs. Try and run dos2unix on the .tcl files and see if they work.

[HuMan321]

Thanks Zen,
That didn't happen here

[HuMan321]

Thanks for the reply. I did transfer in binary, several different times in fact just to make sure. It seems I cannot run either of the tcl's in the superpatch. I downloaded it again and used winrar to unzip and transferred binary and keep getting the same errors
Here is some telnet paste
bash-2.02# superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001
bash-2.02# tivosh superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001
bash-2.02# chmod 755 superpatch-67all-NutKase-1.0.tcl
bash-2.02# superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001
bash-2.02# tivosh superpatch-67all-NutKase-1.0.tcl
InitializeProgramOrDie (tivosh) failed: 0x11001


Update
I started over from the beginning and everthing worked as it should. Must have made some mistake somewhere.

[bdealdb]

I have succesfully upgraded three DVR40's. Thank you very much for Superpatch-67all.

Is there a simple way to remove the 30sec skip AFTER the patch has been applied?

[szurlo]

I have searched this board and tivocommunity and read a bunch of posts on this subject, but have seen about as many differing opinions on this topic as posts. What I want to know, if anyone really knows for sure, is, is there really any "danger" of keeping the phone line hooked to a 6.2 superpatched dtivo to facilitate PPV purchases from the remote. In my case I have only one tivo, so MRV will not be used. ALL I want the superpatch for is HMO. So here I am running an approved sw version on an approved device, with a feature enabled, (HMO), which is available for free to series 2 SA users (right?). Am I really doing anything "wrong" that the phone call could "rat me out" for, besides fiddling with the innards of my dtivo? Or is simply tampering with the software on the Tivo the "offense" we don't want to report? I have seen a few people argue that we don't want to draw attention to what we are doing to our tivos by letting hacked tivos phone home. I could be wrong on this, (wouldn’t be the first time), but I'm pretty sure they know full well what we are doing to our tivos ;) Tivo hacking is not exactly the secret domain of a handful of Linux gurus anymore. Also, since I have seen where some people DO leave their hacked tivos connected, to no obvious ill effect, then if the "mother ship" is learning of all this through the phone calls, it doesn't seem to care. Obviously, a new software version coming down the phone (or sat) can blow away all your hacks, but I wouldn't consider that a "counter measure" on DirecTV’s part. It really seems like they don't care what we do to these things. Obviously theft of service would be a different issue altogether, but that is not what we are talking about here? Or are we? Are we "stealing" HMO? Are we in violation of some agreement we commit to when we buy service from DirecTV?
Ultimately I guess what I'm hoping to hear is a real, known, technical or legal reason why phoning home should not be allowed with a superpatched 6.2 Dtivo.
Anyone have that info?
Steve

[EvilJack]

There is no definitive answer...

It's kind of like running with with scissors....
you should NOT do it, it will probably be ok, and if something
happens, you'll really, really wish that you had followed the
orignial advice.

Picture yourself lying in a heap with a pair of shap scissors
sticking in your chest.... ... thinking... I should not have been
running with sciss.... ( sound of dying goes here )

Picture DTV running a database check and determining that
you have DTV and Tivo and HMO and sending a deactivate
signal to your card becuase the MPAA told them to or they
would sue DTV if DTV didn't put a stop to this. ( would the
MPAA threaten to sue... nah... )

jack

[szurlo]

Eviljack,

Yeah, that's kind of what I was afraid of... The answer is really "letting a hacked Tivo call home doesn't sound like a good idea, so let's be on the safe side and not let it do it". Hate to lose the PPV order feature but I really want HMO. Guess I will have to teach the wife to order PPV from the web ;)

Thanks

[The Only Druid]

Ultimately I guess what I'm hoping to hear is a real, known, technical or legal reason why phoning home should not be allowed with a superpatched 6.2 Dtivo.

This is highly frustrating. I've answered this question (as have others) quite explicitly. If you dial-home after having superpatched your 6.2 dtivo, your unit will download certificates for the HMO/MRV features, with a six-month deadline. This means that, in six months, your certificates will expire and you will be unable to renew them.

It's a rather stupid thing to let happen, since until you dial home, your superpatched system doesn't need the certificates.

As for legal issues: while I'm fairly certain it isn't illegal to hack your unit, DirecTV could easily argue that by enabling HMO/MRV, you're stealing service. It's a grey area, compared to things like tytool or mfs_ftp, and you're taking a risk by letting them possibly find out.

[Lost Dog]

I have succesfully upgraded three DVR40's. Thank you very much for Superpatch-67all.

Is there a simple way to remove the 30sec skip AFTER the patch has been applied?

Do a search for a thread on tivoapp patches. That should give you the original and modified hex values and their location. Hexedit the Tivoapp (either via hex editor or dd) back to the original value. I don't know your skill level at all of this but if you're fairly new, it's really not that complicated.

I *think* that AlphaWolf gave an explanation on how to use the dd command to hex edit in his thread on removing encryption (if the same info is not in the tivoapp patch thread...)

[szurlo]

This is highly frustrating. I've answered this question (as have others) quite explicitly......

Sorry TheOnlyDruid,

I honestly tried to find this info myself, but I appear to be rather inept at finding things in these boards. My problem is that if the title of the thread returned by a search does not appear to be relevent I usually skip over it. My bad.
So after I read your response I resigned myself to reading even the seemingly unrelated posts, and lo-and-behold, I found your answer in a post titled "6.2, Failed while preparing data.", of all places. In that post you say "Specifically, the problem is this: if you don't call home after using the Superpatch, your system will run fine in perpetuity. If you do call home, your system will download MRV keys which expire every 180 days....."

So again, my apologies, and thanks for repeating this answer for me. :) I guess I expected there to be a thread titled "Why you can't let a hacked tivo phone home" :D
I'll try to dig a little deeper next time before I ask.

Steve Z

[The Only Druid]

Sorry TheOnlyDruid
Don't worry about it; you asked a reasonable question in the right thread, so at least you were on the right track. It's just frustrating because it's so common (i.e. I have no particular recollection of you making such a mistake before).

I guess it's also frustrating because about two weeks ago I posted this (http://dealdatabase.com/forum/showpost.php?p=224313&postcount=11), providing just this information when someone asked. At least that wasn't in this thread, so you weren't completely off base.

[scotter72]

I have a Philips DSR704 Series 2 DirectTivo unit with a PTVUpgrade drive. Upgraded to 6.2 from DirecTV. Installed PTVNet CD to get telnet, FTP utilities reloaded. Telneted into system. Got a BASH prompt. FTP'd over the superpatch-67all-NutKase-1.0.tcl and set_mrv_name_67.tcl files as binary to /var/hack folder. cd'd to that folder. Did CHMOD 755 to both .tcl files. Ran ./superpatch-67all-NutKase-1.0.tcl. Got success message. Ran ./set_mrv_name_67.tcl Living_Room_DTivo
Typed in reboot. System came up to "Welcome Powering up..." screen and has not changed. Cannot ping ip address anymore.

Any ideas on how to fix this please? Thanks.

[hxmiller]

search by title (demo) option, FWIW I have found a way to remove this particular menu entry, but its a bit messy.

Can you share the "messy" way to remove the feature? I'd like to do the same with the Promo menu as well.

[AhoyMatey]

I have a Philips DSR704 Series 2 DirectTivo unit with a PTVUpgrade drive. Upgraded to 6.2 from DirecTV. Installed PTVNet CD to get telnet, FTP utilities reloaded. Telneted into system. Got a BASH prompt. FTP'd over the superpatch-67all-NutKase-1.0.tcl and set_mrv_name_67.tcl files as binary to /var/hack folder. cd'd to that folder. Did CHMOD 755 to both .tcl files. Ran ./superpatch-67all-NutKase-1.0.tcl. Got success message. Ran ./set_mrv_name_67.tcl Living_Room_DTivo
Typed in reboot. System came up to "Welcome Powering up..." screen and has not changed. Cannot ping ip address anymore.

Any ideas on how to fix this please? Thanks.Serial cable output? Pull drive and check boot params? Ensure that a killhdinitrd kernel is dd'ed to the correct partition?

[scotter72]

Serial cable output? Pull drive and check boot params? Ensure that a killhdinitrd kernel is dd'ed to the correct partition?
Yes, there is a serial cable output... but alas I did not have a serial cable. So, I just ordered one online from 9th Tee. (Not sure if Radio Shack or Best Buy would have one). Could you direct me to or explain in newbie terms what you mean by that last statement please? Not very Linux savvy. Sorry. :(

[Gildor57]

Yes, there is a serial cable output... but alas I did not have a serial cable. So, I just ordered one online from 9th Tee. (Not sure if Radio Shack or Best Buy would have one). Could you direct me to or explain in newbie terms what you mean by that last statement please? Not very Linux savvy. Sorry. :(

No, RS does not sell the cable, but they sell the parts to make your own.

As to what was meant...

"Serial cable output?" - Post the serial cable output, so we can see exactly what is happening when you boot. It is next to impossible to trouble shoot based on limited information. In fact, many of the more knowledgable people here will not help at all unless you show that output because its a waste of time trying to debug a problem with only vague and imprecise information.

"Pull drive and check boot params?" - When your hard drives are mounted in a PC and booted up in Linux, what does the "bootpage -p" command give you as a result?

"Ensure that a killhdinitrd kernel is dd'ed to the correct partition?" - What command (and what form of the command) did you use to copy your killhdinitrd'ed kernel to your boot partition? And when you did it, did you send it to the correct partition?

If you wish to hack your Tivo in any kind of reliable fashion, you will have to get Linux "savvy". No getting around it.

[brywalker]

Absolutely fantastic work!

Only complaint is that it moves Standby to the 2nd page (much harder to do it when the TV is off!).

My hats off to you NutKase!!

[NutKase]

Don't worry about it; you asked a reasonable question in the right thread

No offense meant here but, it's my position that he asked a reasonable question in the WRONG thread.

Phone home discussions deserve a new home as they aren't actually superpatch-67all related. His questions just came up after he applied the patch.

Maybe this one. (http://www.dealdatabase.com/forum/showthread.php?t=43935)

HuMan321, szurlo, and those who answered their off-topic questions should pay closer attention to this thread's purpose. OTOH, I see that several OT posts have already been split off. Thanks mods.


NutKase

[NutKase]

No, RS does not sell the cable, but they sell the parts to make your own.

As to what was meant...

"Serial cable output?" - Post the serial cable output, so we can see exactly what is happening when you boot. It is next to impossible to trouble shoot based on limited information. In fact, many of the more knowledgable people here will not help at all unless you show that output because its a waste of time trying to debug a problem with only vague and imprecise information.

"Pull drive and check boot params?" - When your hard drives are mounted in a PC and booted up in Linux, what does the "bootpage -p" command give you as a result?

"Ensure that a killhdinitrd kernel is dd'ed to the correct partition?" - What command (and what form of the command) did you use to copy your killhdinitrd'ed kernel to your boot partition? And when you did it, did you send it to the correct partition?

If you wish to hack your Tivo in any kind of reliable fashion, you will have to get Linux "savvy". No getting around it.

DO NOT start supporting normal non-superpatch-67all related tivo newbie hacking questions in this thread.

DO NOT ask for, or post, boot/serial output in this thread.

Refer to my first post in this thread. I guess I should continue to add to the list. Don't ask for help with, or support:

killhdinitrd
Boot problems
Phone call home issues
linux

in the superpatch-67all thread...


NutKase

[darrin75]

Quick question, is it possible to edit the script so that only mrv is applied without the music & photos. The reason I am asking is I Never use the music & photos and would much rather have the standby button on the main screen. Is this possible, what lines need to be commented out..Thanks for the great work by the way.. :D

[rbautch]

I've seen no mention here or in the release thread whether or not superpatch-67all disables call-in nag screens. If it does, I assume there's no conceivable reason for running fakecall.tcl regularly, other than to eliminate the need for an initial call. True?

[hayreass]

It does appear to be true.
I've had 6.2 going for quite a while now without fakecall, and there are no ill effects.

[Stephanie]

Guys,

Hoping you can give me some guidance of what else to research to solve my problem.

First, here is my background and environment:
Superpatch67 an HDVR2 6.2 w/160G drive that I let Tivo u/g from the image expanded from the orig drive - modded w/ a PTVupgrade 3.1.5 Killhdinitrd kernel.
Superpatch4all an HDVR2 4.01b w/160G drive (monte)
Superpatch4all an HDVR3 4.01b w/160G drive (monte)
Superpatch4all an DVR40 4.01b w/160G drive (monte)
Superpatch4all an Phillips DSR70 4.01b w/160G drive (monte)
Unmodded/hacked Pioneer 810H SA Tivo lifetime (subbed) 5.x - going to wait on this one - hopefully my beta application will come through :)
- SetMRV with ADH version for the 4.01b DireTivos
- Flat 192.x.x.x network full duplex.

So the weird thing that I haven't seen anyone else come up against (hopefully I didn't miss a post - my apologies if I have) :

The 6.2 can only see the 810H (of course the certs don't match & 5.x so I can't exchange - but at least it's in the NowPlaying)
All of the 4.01b's can see each other AND the 6.2 but can only exchange (MRV) with the other 4.01b's. They also see the 810H and get the " programs cannot be transferred from the 810H onto the 401b tivo....." - not worried about this issue and as above will wait for 7.x on it.

So what is Driving me nuts is that when I try to access the 6.2 from a 4.01b I get throught the NowPlaying list (with an entry for the 6.2 Tivo and the Watch on this TV for one of the Movies in the NowPlaying list and it looks like the transfer is about to begin but then BOOM after a few seconds I get a screen titled "CAN'T WATCH NOW" with the text "Sorry, you can't watch this program now, either because the 6.2 Tivo is no longer available on the network or because the requested program could no longer be found. Before trying again, make sure that the 6.2 Tivo is turned on, connected to the network, has the correct network settings, and still contains the program you want to watch"

I'm eventually going to convert all of the other 4.01b's to 6.2 and I'll bet good money that I won't have this issue but it has my attention and I'd love to figure out why it isn't working.

Love to hear what anyone thinks about this!
Thanks in advance!!

-- Steph

[PlainBill]

Guys,



So the weird thing that I haven't seen anyone else come up against (hopefully I didn't miss a post - my apologies if I have) :

The 6.2 can only see the 810H (of course the certs don't match & 5.x so I can't exchange - but at least it's in the NowPlaying)
All of the 4.01b's can see each other AND the 6.2 but can only exchange (MRV) with the other 4.01b's. They also see the 810H and get the " programs cannot be transferred from the 810H onto the 401b tivo....." - not worried about this issue and as above will wait for 7.x on it.

So what is Driving me nuts is that when I try to access the 6.2 from a 4.01b I get throught the NowPlaying list (with an entry for the 6.2 Tivo and the Watch on this TV for one of the Movies in the NowPlaying list and it looks like the transfer is about to begin but then BOOM after a few seconds I get a screen titled "CAN'T WATCH NOW" with the text "Sorry, you can't watch this program now, either because the 6.2 Tivo is no longer available on the network or because the requested program could no longer be found. Before trying again, make sure that the 6.2 Tivo is turned on, connected to the network, has the correct network settings, and still contains the program you want to watch"

I'm eventually going to convert all of the other 4.01b's to 6.2 and I'll bet good money that I won't have this issue but it has my attention and I'd love to figure out why it isn't working.

Love to hear what anyone thinks about this!
Thanks in advance!!

-- Steph

The only thing that comes to mind is networking - how did you set the ip address on the 6.2 DirecTiVo?

PlainBill

[Stephanie]

Thanks for the reply PlainBill!
I used DHCP on the 6.2. I've since found this thread http://www.dealdatabase.com/forum/showthread.php?t=43375 not sure why I didn't find it in my first search. After reading it over several times, it IS directly related to what I'm experiencing. I think I'll experiment with the setup when I get home from school. It sounds like I need to get a network sniffer - any suggestions as to which one is best?
It's great to see that DDB is not only a Linux OS / Linux application space to learn from but also a networking site to learn from!! Thanks again guys!

-- Steph

[gudgolf]

Question, is the "superpatch-67" compatible with a Ptvugraded Samsung Sir4040 with a new 160gb drive?

[NutKase]

Question, is the "superpatch-67" compatible with a Ptvugraded Samsung Sir4040 with a new 160gb drive?

Superpatch-67all is compatible with the tivo software versions listed in the release post.

The matter of hacking your tivo is not relevant.

When you figure out what the p t v upgrade products did to your tivo you may be able to use advanced hacks and other programs. Until then stop asking about these products and what works with them in my thread.


[EDIT] First post updated with another thing off-topic in this thread.


NutKase

[ihavenoidea]

I have a Series 2 runnung 6.2. When I execute superpatch, this is what I get.


bash-2.02# bash superpatch-67all-NutKase-1.0.tcl
superpatch-67all-NutKase-1.0.tcl: array: command not found
superpatch-67all-NutKase-1.0.tcl: 0xff7fd4: command not found
superpatch-67all-NutKase-1.0.tcl: 0x93bc8c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x0050e46c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x0050e4c4: command not found
superpatch-67all-NutKase-1.0.tcl: 0x0050e53c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x0050eb5c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x0050ee48: command not found
superpatch-67all-NutKase-1.0.tcl: 0x00511654: command not found
superpatch-67all-NutKase-1.0.tcl: 0x00511978: command not found
superpatch-67all-NutKase-1.0.tcl: 0x0062772c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x00691284: command not found
superpatch-67all-NutKase-1.0.tcl: 0x01259ebc: command not found
superpatch-67all-NutKase-1.0.tcl: 0x01262d6c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x01327aa8: command not found
superpatch-67all-NutKase-1.0.tcl: 0x01327ab0: command not found
superpatch-67all-NutKase-1.0.tcl: 0x01327ab8: command not found
superpatch-67all-NutKase-1.0.tcl: 0x0146c1d4: command not found
superpatch-67all-NutKase-1.0.tcl: 0x015a87f4: command not found
superpatch-67all-NutKase-1.0.tcl: 0x015a953c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x015a95d4: command not found
superpatch-67all-NutKase-1.0.tcl: 0x015a9ba8: command not found
superpatch-67all-NutKase-1.0.tcl: 0x015a9d4c: command not found
superpatch-67all-NutKase-1.0.tcl: 0x015aa438: command not found
superpatch-67all-NutKase-1.0.tcl: line 64: syntax error near unexpected token `}
'
superpatch-67all-NutKase-1.0.tcl: line 64: `}'
bash-2.02#
bash-2.02#


What am I doing wrong?

[PlainBill]

I have a Series 2 runnung 6.2. When I execute superpatch, this is what I get.


bash-2.02# bash superpatch-67all-NutKase-1.0.tcl
superpatch-67all-NutKase-1.0.tcl: array: command not found

bash-2.02#
bash-2.02#


What am I doing wrong?

How did you transfer it to the TiVo?

PlainBill

[eastwind]

I have a Series 2 runnung 6.2. When I execute superpatch, this is what I get.


bash-2.02# bash superpatch-67all-NutKase-1.0.tcl

<SNIP>

superpatch-67all-NutKase-1.0.tcl: line 64: `}'
bash-2.02#
bash-2.02#


What am I doing wrong?
Don't bash it. It's a tivosh script.

ew

[ihavenoidea]

Don't bash it. It's a tivosh script.

ew

Duh, ok so I'm an *****. That worked like a champ. Thanks for your help.

[jkozee]

KNOWN ISSUES
6.x
6.1 (R10) tivoapps are not supported. May be supported in a future release.


Any chance that 6.1 will ever find its way into the superpatch?

[darrin75]

If it does how do you expect to run it. As far as I know the R10 is not hackable without some soldering modifications. But, then again I don't know that much about the R10 units. Good luck

[jkozee]

Yeah, the R10 would require a prom mod to run the hack. But I thought the reason it wasn't included was because it was suspected that the R10 could easily run 6.2, but according to this thread that doesn't seem to be the case.
http://www.dealdatabase.com/forum/showthread.php?t=39927&page=4

[usa11usa]

:confused:
Hi, I have s. looked in this fourm but did not see any help in this. here is the problem

i have hdvr2 80gig drive runing 6.2.
i installed the hmo patche and it worked fine for 2 day.
what i cant see is the list of the 4 other tivos i have. the others are working fine and can see each other in the now playing list. the one tivo running 6.2 does have an ip and can use the other parts of the hmo patch list music and photos. it is just the now playing list that does not display the other tivos in the house. and the hdrv2 running 6.2 does not displayed on the other tivos.

if more info is needed please tell me what i need to tell you


fyi. i do have ftp and telnet access. :confused:

[PlainBill]

:confused:
Hi, I have s. looked in this fourm but did not see any help in this. here is the problem

i have hdvr2 80gig drive runing 6.2.
i installed the hmo patche and it worked fine for 2 day.
what i cant see is the list of the 4 other tivos i have. the others are working fine and can see each other in the now playing list. the one tivo running 6.2 does have an ip and can use the other parts of the hmo patch list music and photos. it is just the now playing list that does not display the other tivos in the house. and the hdrv2 running 6.2 does not displayed on the other tivos.

if more info is needed please tell me what i need to tell you


fyi. i do have ftp and telnet access. :confused:
How are you setting the ip address?

PlainBill

[usa11usa]

How are you setting the ip address?

PlainBill

I set it in the rc.sysinit.author file

[dave4089]

USA,

I have a DSR704 and DSR708 that I recently upgraded to 6.2. If I used ifconfig to set the IP address in rc.sysinit.author, they would not see each other. I had to used netconfig.tcl which sets the IP address and related information into the MFS database. I believe that this emulates what would happen if you could set the IP address from the Tivo menus. netconfig.tcl can be found in the following thread:

http://www.dealdatabase.com/forum/showthread.php?t=43375&page=1&pp=15&highlight=netconfig.tcl

I beleive the version I used is in post #24.

netconfig.tcl only has to be run once to set the IP address, etc. It does not need to be run everytime you boot.

From what I understand, that when you set the IP address in rc.sysinit.author, this is too late in the boot process to allow the Tivos to see each other.

Dave

[PlainBill]

I set it in the rc.sysinit.author file
Note Dave 4089's post, AND you must also disable the dhcp client. Did you even read this (http://www.dealdatabase.com/forum/showthread.php?t=42325) thread?

PlainBill

[7.1]

Note Dave 4089's post, AND you must also disable the dhcp client. Did you even read this (http://www.dealdatabase.com/forum/showthread.php?t=42325) thread?Not to mention this (http://www.dealdatabase.com/forum/showthread.php?t=43375) thread on the problem, and this (http://www.dealdatabase.com/forum/showthread.php?p=222641#post222641) summary post in the very thread where you posted your question. Please read all the posts in a thread before adding a new post on the end. There's a pretty good chance the issue has been covered before.

[jbebel]

I looked through the thread, and didn't see anything like this, so I'm not sure what I did wrong. Did I miss something obvious? When I run the superpatch, I get this and the tivo immediately restarts:

bash-2.02# ./superpatch-67all-NutKase-1.0.tcl
assert: Tmk Assertion Failure:
assert: FsAllocateFunction, line 203 ()
Tmk Fatal Error: Thread tivosh <314> strayed!
Paste the following into a shell to get a backtrace...

bt -t /tvbin/tivoapp <<END_OF_BT
tcd 1
hpk Series2
read 0x2aaa8000 /lib/ld.so.1
read 0x2ab04000 /lib/libhpkoss.so
read 0x2ab50000 /lib/libtvstructures.so
read 0x2abac000 /platform/lib/libhpkhl.so
read 0x2ac58000 /lib/libtmk.so
read 0x2ad3c000 /lib/libtvutil.so
read 0x2ada4000 /platform/lib/libhpkll.so
read 0x2ade8000 /lib/libutil.so.1
read 0x2ae2c000 /lib/libdl.so.2
read 0x2ae70000 /lib/libpthread.so.0
read 0x2aecc000 /lib/libm.so.6
read 0x2af94000 /lib/libc.so.6
read 0x2b130000 /lib/libcdaudio.so
0x2acdfd08 0x00876708 0x2acb2c4c 0x2acaa274 0x2acb1818 0x013807b8 0x01380178
0x008f8dc4 0x0094d198 0x2afa53fc
END_OF_BT

Tmk Fatal Error: Thread tivosh <314>: assertion failure

[Jamie]

Did I miss something obvious?Search, titles only, for "FsAllocateFunction".

[jbebel]

Oh yeah! That's what I forgot. Thanks Jamie.

[jbebel]

Well, now everything seems to working almost exactly as expected, except for one thing. restarting. When I type restart, I get the following, and a blank green tivo central screen on the TV:

bash-2.02# restart
Killing processes...
bash: [12: 2] tcsetattr: Inappropriate ioctl for device
bash-2.02# HPK: Trying to stop the program...
Logger not initialized! Logging to stdout:
TmkLogger: <131>Aug 9 08:01:12 TmkMempool[97]: Memory leak in mempool MempoolGlobals: 75 blocks not freed
assert: Tmk Assertion Failure:
assert: ReportLeak, line 267 ()
Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 TmkAssertionFailure[97]: : (ReportLeak, line 267 ())
Tmk Fatal Error: Thread (null) <97> strayed!
Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: Tmk Fatal Error: Thread (null) <97> strayed!
Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: bt -t /tvbin/fancontrol
Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: tcd 1

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: hpk Series2

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2aaa8000 /lib/ld.so.1

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2ab04000 /platform/lib/libhpkhl.so

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2abb0000 /lib/libhpkoss.so

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2abfc000 /lib/libtmk.so

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2ace0000 /lib/libdl.so.2

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2ad24000 /lib/libtvutil.so

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2ad8c000 /platform/lib/libhpkll.so

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2add0000 /lib/libm.so.6

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2ae98000 /lib/libc.so.6

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2b034000 /lib/libpthread.so.0

Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: read 0x2b090000 /lib/libcdaudio.so

0x2ac83d08 0x2ac69ff0 0x2ac4a6b8 0x2ac4ab04 0x2ac4fd98 0x2ac69e60 0x2ac48d8c
Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: 0x2ac83d08 0x2ac69ff0 0x2ac4a6b8 0x2ac4ab04 0x2ac4fd98 0x2ac69e60 0x2ac48d8c
0x2ac57780 0x2ac5c168 0x2ac5bc4c 0x2ac54c04 0x2abb4ea8 0x00401d94
Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: 0x2ac57780 0x2ac5c168 0x2ac5bc4c 0x2ac54c04 0x2abb4ea8 0x00401d94
END_OF_BT

Tmk Fatal Error: Thread (null) <97>: assertion failure
Logger not initialized! Logging to stdout:
TmkLogger: <129>Aug 9 08:01:12 Thread (null)[97]: Tmk Fatal Error: Thread (null) <97>: assertion failure
Changing thread name to ***Thread (null)
Start debugger remote while I sleep
Wake address 0x10006129


My bash prompt still works after this, so if I type restart again, I get this:

bash-2.02# restart
Illegal read at 00000000
do_page_fault #2: sending signal 11 to restart(301)
$0 : 00000000 fefefeff 00000001 00000000 00000000 00000018 00000000 00000054
$8 : 00000054 7fff7fdc 00000000 00000001 0000a000 00000000 00100000 00000061
$16: 00000000 00000000 5fa70158 7fff6b40 0094d168 1000e30c 017d90c8 00000000
$24: 00000000 2ac7f310 2ad3de00 7fff6990 1001baac 2ac883fc
Hi : 00000000
Lo : 00000000
epc : 2ac7f33c Not tainted
Status: a001fc13
Cause : 00000008
8001dac0 8001dadc 80021c04 80021dc4 80023e18 2ac7f33c
2ac7f33c 2ac883fc 2acb525c 2aca6328 2aca8600 2acb254c 2acaa274 2acb1818
013807b8 01380178 008f8dc4 0094d198 2afa53fc
bash: [12: 2] tcsetattr: Inappropriate ioctl for device


The only way I seem to be able to restart it is with the reboot command or the power cord. Any thoughts what this indicates?

Joel

[jasch]

Any chance it should be safe to try this on 7.2 <grin>

Just wondering if already somebody found if the hex edit is similar to 7.1x

[jkozee]

Here are what I believe to be the patch locations for 6.1. I do not have a DTivo to test this on, althogh I did do a pseudo test using a standalone Humax attempting to run 6.1 (don't ask - I was board. Wish I could've gotten the tuner working for the cable), and it seems the patches work, but I'd say this was far from conclusive.

If anyone (with a good backup - and prepared to use it) wants to test this, I'll ask Nutcase to add this into the script if it pans out.

# 6.1 Requires set_mrv_name_67.tcl
# The first two patches are 30 second skip & backdoors

array set patch_6_1 {

0x00a67728 "1040001d 1440001d"
0x00ae4bec "00008821 24100001"

0x0053412c "00408021 24100001"
0x00542fe4 "00408021 24100001"
0x0055a9d4 "00408021 24100001"
0x00619f00 "00408021 24100001"
0x00640f7c "00408821 00008821"
0x00640fa0 "00408821 00008821"
0x00899d80 "0320f809 24020000"
0x00a86f00 "1040026d 00000000"
0x00B3C9A4 "3c1c0f53 03e00008" 0x00B3C9A8 "279c0dac 24020001"
0x00D7CD94 "0320f809 00001021"
0x00d864a4 "10400043 00000000"
0x00d8d728 "0320f809 24020000"
0x00dc756c "0320f809 24020001"
0x00e3536c "0320f809 3c020000"
0x00e35468 "8f998280 8e440010" 0x00e3546c "00000000 8c820000"
0x00e35470 "27394ec8 8c850004" 0x00e35474 "0320f809 00451025"
0x00e35478 "00000000 8c850008" 0x00e3547c "8fbc0010 00451025"
0x00e8a2a0 "3c1c0f1e 03e00008" 0x00e8a2a4 "279c34b0 24020001"
0x00e8b0fc "0320f809 00001021"
0x00e8b194 "0320f809 00001021"
0x00e8b74c "0320f809 00001021"
0x00e8b8f0 "0320f809 00001021"
0x00e8bcb0 "0320f809 00000000"
0x00e8bfdc "0320f809 00001021"
0x01131460 "0320f809 24020000"
0x0124580c "02001021 24020001"
0x013667b0 "8c820004 03e00008" 0x013667b4 "8cab0000 00000000"
0x01366d64 "8c820048 03e00008" 0x01366d68 "8cab0000 00000000"
}

BTW, you'll obviously need to add the following to the code section that determines the Tivoapp vresion.
...
} elseif { [regexp {^6\.1} $sw] } {
set a "patch_6_1"
...

[EDIT]
OOPS If this should be in the development thread please move it - sorry and thanks.

[jasch]

superpatch-67all-NutKase-1.0.tcl
(C) 05/08/2005 by NutKase, et al - COMMERCIAL USE PROHIBITED

Credit goes to CapablePerson66, rc3105, and others who wish to
remain anonymous. We thank ESPECIALLY alldeadhomiez for his time and knowledge.

All errors are the fault of Anonymous :-) .

Your TiVo Software version is 6.1-01-2-521
Please write down your TiVo Software version.


Checking your tivoapp patch locations...

Patching your tivoapp...

Success!
________
1. Your 6.1-01-2-521 tivoapp was updated with the proper superpatch-67all
2. Your original tivoapp was backed up and is called /tvbin/tivoapp.original.
3. You'll need to run the set_mrv_name_67.tcl, I've included, to 'name' your tivo.

I'll let you know after I reboot :-)

[jasch]

Thanks a lot! Now I can see my other Tivos :-)

Music and Photos: OK
MRV: Receive (PULL) OK, Transmit (PUSH) OK
NOCSO: OK

Any specifics to try/test?

[jkozee]

jasch,

I'll send you a PM. Glad to hear it works.

[wesmoc]

Just upgraded to 6.2 and rebooted the system. I was able to telnet in and finish up some of the post-install stuff. I noticed that it would no longer play any of the video I had on the unit (selecting play would immediately act as if it got to the "end" of the show and asked to delete it), and, since I had not applied the superpatch, I figured that would help.

I applied the superpatch, rebooted, and, while the tivo came back up, it still wouldn't play my unencrypted video. Additionally, I could no longer telnet to the box! Argh..

I'll have to rip the drive back out of the tivo and try to see what's up with it, but I am not sure what I am looking for at this point.

Do you think it is just coincidental that telnet died after performing the superpatch?

[jasch]

Do you think it is just coincidental that telnet died after performing the superpatch?

Definitely. The only thing the SuperPatch does is modify Tivoapp slightly, and Tivoapp has nothing to do with the network or bash access.

[wesmoc]

I applied the superpatch, rebooted, and, while the tivo came back up, it still wouldn't play my unencrypted video.

For other reasons (the new tserver, for one), I downloaded the MIPS version of the Unified mfs_utils (http://www.dealdatabase.com/forum/showthread.php?t=39487), installed them, and saw the "ciphercheck" script. So, I ran it:

bash-2.02# ./ciphercheck
CipherCheck - based on CipherCheck.tcl by AlphaWolf_HK

TyStream encryption is currently disabled.

Here is the status of your current recordings:

Encrypted CSO Set Stream Name
--------- ------- -----------
No No Pink Panther
No Yes Pink Panther
No Yes Law & Order
No Yes Law & Order
No Yes Scooby-Doo, Where Are You!
No Yes Law & Order
No Yes Teen Titans
No Yes Totally Spies
...

(Hey, my kids use the Tivo, too.) Obviously, now, it looks like it is having trouble because CSO is set for all of the old video, but the system doesn't have CSO set.

Is there a way to set CSO back on so I can view all of the old video? Is there a reason not to have this on? I have no idea (yet) what CSO stands for....

Additionally, I could no longer telnet to the box! Argh..

Eh.. I was being impatient. There was a "sleep 300" line in rc.sysinit.author, and I wasn't waiting 5 minutes. So, this wasn't a result of the superpatch at all.

[jasch]

Is there a way to set CSO back on so I can view all of the old video? Is there a reason not to have this on? I have no idea (yet) what CSO stands for....

The patch in the SuperPatch is for NoCSO, so you would have to remove the patch to watch the videos. (the Tivo by default can watch unencrypted videos without any problems, or videos recorded by itself. With superpatch you can watch anything recorded on other tivos or extract).

Eh.. I was being impatient. There was a "sleep 300" line in rc.sysinit.author, and I wasn't waiting 5 minutes. So, this wasn't a result of the superpatch at all.

Actually, you only need to do the sleep before TiVoweb, since it sometimes gives problems when you start it up too quickly while the box is still finishing up.

If you're not using tivoweb you can get rid of the sleep.

[PlainBill]

For other reasons (the new tserver, for one), I downloaded the MIPS version of the Unified mfs_utils (http://www.dealdatabase.com/forum/showthread.php?t=39487), installed them, and saw the "ciphercheck" script. So, I ran it:

bash-2.02# ./ciphercheck
CipherCheck - based on CipherCheck.tcl by AlphaWolf_HK

TyStream encryption is currently disabled.

Here is the status of your current recordings:

Encrypted CSO Set Stream Name
--------- ------- -----------
No No Pink Panther
No Yes Pink Panther
No Yes Law & Order
No Yes Law & Order
No Yes Scooby-Doo, Where Are You!
No Yes Law & Order
No Yes Teen Titans
No Yes Totally Spies
...

(Hey, my kids use the Tivo, too.) Obviously, now, it looks like it is having trouble because CSO is set for all of the old video, but the system doesn't have CSO set.

Is there a way to set CSO back on so I can view all of the old video? Is there a reason not to have this on? I have no idea (yet) what CSO stands for....


Eh.. I was being impatient. There was a "sleep 300" line in rc.sysinit.author, and I wasn't waiting 5 minutes. So, this wasn't a result of the superpatch at all.

Obviously, you originally hacked your DirecTiVo using TiVoScripts and never bothered to upgrade from the kmem hack. The solution is simple - run csoscout (search for it, then read the first few posts in the thread).

By the way, the kmem hack was not the only outdated hack installed by TiVoScripts. I hope you didn't just move everything over to 6.2.

PlainBill

[wesmoc]

Found it. :)

The answer was in this thread (http://www.dealdatabase.com/forum/showthread.php?t=31213).

Have I mentioned that this forum rocks? :)

[wesmoc]

The real history here is that I bought the Samsung 40GB DirecTivo. I hacked it with the Sleeper ISO. I then upgraded to the 120GB drive I have now. Added a bunch of hacks (tivoweb (then tivowebplus), tserver, mfs_ftp, ssh, elseed). 8months later, I cleaned up the problems with the sleeper install (I believe you helped me a bit there, BTW), migrated the start scripts to be utilized by the TPM (tivo package manager) type of install, and moved over to the killhdinitrd kernel (3.1.1e).

I have now just upgraded to 6.2 (backed up the 120 using mfsbackup/restore to another drive) with its numerous steps to install my 3.1.5 killhdinitrd'ed kernel, move over my hacks, edit rc.sysinit.author (and rc.sysinit such that it calls rc.sysinit.author!), and a bunch of other things including installing the mfs_utils bundle to get the latest tserver (that doesn't use NowShowing). I've just completed the run of csoscout.tcl which worked beautifully.

I've still got some other steps to do:
o need to figure out why my ssh keys aren't working, but that's no big deal
o need to figure out why TivoWebPlus won't show the NowShowing data (it might be as simple as a reboot since I already made the version change)
o Need to look in to mfs_ftp to see what's up with that.. it's not running.

Once that's complete, I'll look in to the backported drivers to improve the USB performance.

Thanks!

Obviously, you originally hacked your DirecTiVo using TiVoScripts and never bothered to upgrade from the kmem hack. The solution is simple - run csoscout (search for it, then read the first few posts in the thread).

By the way, the kmem hack was not the only outdated hack installed by TiVoScripts. I hope you didn't just move everything over to 6.2.

[naxet]

Is there a project to provide 7.2 software support to the superpatch. I just got the update. I am think about reintalling a backup image with 7.1b so I can get MRV working with my Dtivo running 4.01b, but from reading that can lead to problems as well.

[7.1]

Here's a candidate patch that adds support for 7.2.0. There are three variations included: -elm- (Toshiba/Humax S2.5 DVD), -tak- (Pioneer S2 DVD) and -oth- (everything else). Only the -oth- patch has been tested.

This is in the form of a patch against superpatch-67all-NutKase-1.0.tcl. Apply via "zcat sp-1.0-to-1.1.patch.gz | patch" in the directory where you have superpatch-67all-NutKase-1.0.tcl. If you don't have a working zcat or patch program on your tivo, run this on your PC under cygwin or on a linux box. You can also separate the uncompress and patch steps out into separate commands if you prefer.

If you are unable to apply patches, you aren't a good candidate for alpha testing -- wait for NutKase to incorporate it into a released version. Please, no postings of the form "how do I use this?" Such posts will be silently ignored.

If you try this on an -elm- or -tak- unit, please confirm that it works.

[jasch]

Please, no postings of the form "how do I use this?" Such posts will be silently ignored.

bash-2.02# zcat sp-1.0-to-1.1.patch.gz | patch
sp-1.0-to-1.1.patch.gz: applet not found

Too bad... Guess I'll have to wait for the updated version.

[jasch]

Applied the patch directly

patch superpatch-67all-NutKase-1.0.tcl sp-1.0-to-1.1.patch
patching file superpatch-67all-NutKase-1.0.tcl
Hunk #3 succeeded at 269 (offset -3 lines).

Your 7.2.0-oth-01-2-540 tivoapp was updated with the proper superpatch-67all

[naxet]

bash-2.02# zcat sp-1.0-to-1.1.patch.gz | patch
sp-1.0-to-1.1.patch.gz: applet not found

Too bad... Guess I'll have to wait for the updated version.

Applied the patch directly

patch superpatch-67all-NutKase-1.0.tcl sp-1.0-to-1.1.patch
patching file superpatch-67all-NutKase-1.0.tcl
Hunk #3 succeeded at 269 (offset -3 lines).

Your 7.2.0-oth-01-2-540 tivoapp was updated with the proper superpatch-67all


What did you do inbetween your post?

[jasch]

What did you do inbetween your post?

I only uncompressed the .GZ file

[naxet]

Did the patched patch patch the tivo

[naxet]

Thanks for posting the patch 7.1, I now have MRV running between teh 7.2 stanalone (oth versoin) and my Dtivo.

[NutKase]

A new superpatch-67all (http://www.dealdatabase.com/forum/showthread.php?t=43325) is released. This file covers 7.2.0-* and 6.1 tivoapps.

Thanks to '7.1' and 'jkozee' for their work.


NutKase

[Fletch319]

DELETED - ooops

[jasch]

Superpatch is not for circunventing daily calls.

[scottym]

superpatch-67all reported success after running on a HDVR2 6.2. I also have 2 4.01b TiVos on my subnet. From my newly superpatched TiVo I can see the other 2 DVRs at the bottom of the Now Showing list. When I select one of the 4.01b DVRs I get the following message: "Programs cannot be transferred from the MBR DVR to the 587B DVR because the 587B DVR is not enabled for transfers..."

Has anyone else seen this message? Any idea of what went wrong?

[jasch]

Did you apply the superpatch to your 4.xx units? Even tough they already have MRV, they are only authorized to MRV programs between those Tivo's authorized in your account. Since obviously the 6.2 cannot be authorized, you need to patch the 4.x units as well. If not then you will not be able to transfer programs.

[jasch]

You should also make sure all your 3 Tivos have all the network configuration present (including gateways and DNS)

[scottym]

My 4.x TiVos were patched with superpatch-4all. MRV works between my two 4.x DVRs. But not between my 6.2 and 4.x DVRs. As you suggested, I did configure my other two DVRs with static IP addresses. I used 192.168.1.1 for both my default gateway and DNS addresses on all DVRs-not sure this is okay.

[scottym]

Perhpas I failed to mention that all by DVRs are D* not SA

[PlainBill]

It sounds like you did not run set_mrv_name_67.tcl, or the system called DirecTV after it was run.

PlainBill

[scottym]

It sounds like you did not run set_mrv_name_67.tcl, or the system called DirecTV after it was run.

PlainBill

I ran ./set_mrv_name_67.tcl 2BR. It executed quickly and didn't generate any output. When I checked for access to to my 6.2 TiVo from the 4.x machine my 6.2 machine was reported as 587B instead of the name I gave.

I ran ./set_mrv_name_68.tcl 2BR again with the same results.

It appears my installation has a problem with set_mrv_name. I used PTVnet and Instant Cake to get network access to a bash shell. I'm not sure this is relavant but I did post a message at PTVupgrade to ask if they modified tivoapp and the reply was no. So I'm assuming MRV should work after applying superpatch-67all and set_mrv_name. :confused:

[scottym]

Problem Solved. Newbie mistake. I'll hang my head in shame.

MOD: Please feel free to delete my related posts.

Thanks all.

[fgoodman]

Apologies if this should go in the "MRV networking" thread, but I wasn't sure
so I figured I had to pick. I'll try to make up for any errors in posting
ettiquette (sp?) by providing as much pertinent information as I can.

Quick summary:

6.2 dtivo hacked and running superpatch (v.1.0)
7.1 tivo SAS2 hacked and running superpatch (v. 1.1)

EVERYTHING WORKED FINE:

upgrade 7.1 to 7.2 everything works fine with the network (e.g telnet, bash,
ftp etc.). However, the Tivo's don't see each other so there's no MRV.

Both boxes show MRV enabled under System Information. Both boxes
show "Backdoors enabled" so I know I really did run the superpatch
on each.

From what I've read there should be a "broadcast" statement in the 6.2
tvlog (similar to what I see on the 7.2 box) and instead I only see the
following:


Oct 4 20:33:14 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0


Do I need to flush something on the 6.2 dtivo box? If so, I'd appreciate some
remedial instruction. I know linux pretty well, but MFS and tivosh are still
pretty greek to me.

Can I rerun the superpatch (v 1.1) on the 6.2 box? Will that help or break
things completely?

This all worked perfectly prior to the 7.1 to 7.2 upgrade.

Thanks in advance and apologies if this is the wrong thread...
Frank


Here's the data from each machine:

Dtivo (6.2) Data:


bash-2.02# more /etc/resolv.conf
search localdomain
nameserver 192.168.100.2
bash-2.02#

bash-2.02# netstat -ln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:3105 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3565 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2190 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2191 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:2190 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 72 /var/dev/log
unix 2 [ ACC ] STREAM LISTENING 145 /tmp/S_EventSwitcherSocket101
bash-2.02#

bash-2.02# ping tivo
PING tivo (192.168.100.51): 56 data bytes
64 bytes from 192.168.100.51: icmp_seq=0 ttl=64 time=8.4 ms
64 bytes from 192.168.100.51: icmp_seq=1 ttl=64 time=4.3 ms
64 bytes from 192.168.100.51: icmp_seq=2 ttl=64 time=4.4 ms

--- tivo ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 4.3/5.7/8.4 ms
bash-2.02#

bash-2.02# grep -i broadcast /var/log/tvlog
Oct 4 06:46:46 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0
Oct 4 20:33:14 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0
Oct 5 17:32:26 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0
Oct 5 18:17:45 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0
Oct 5 18:50:50 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0
Oct 5 19:02:08 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0
Oct 6 16:31:09 (none) KnownHostListener[180]: Entry changed: 1400000802237CF "TIVO-S2SA" tcd/Series2 7.2.0-oth-01-2-140 broadcast @ 192.168.100.51 : 0/0
bash-2.02#


Tivo (7.2) Data:


root@tivo [199] # more /etc/resolv.conf
search localdomain
nameserver 192.168.100.2
root@tivo [200] #

root@tivo [197] # netstat -ln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:2190 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2191 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:1024 0.0.0.0:*
udp 0 0 0.0.0.0:2190 0.0.0.0:*
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 87 /var/dev/log
unix 2 [ ACC ] STREAM LISTENING 180 /tmp/S_EventSwitcherSocket92
root@tivo [198] #

root@tivo [198] # ping dtivo
PING dtivo (192.168.100.50): 56 data bytes
64 bytes from 192.168.100.50: icmp_seq=0 ttl=64 time=2.7 ms
64 bytes from 192.168.100.50: icmp_seq=1 ttl=64 time=4.5 ms
64 bytes from 192.168.100.50: icmp_seq=2 ttl=64 time=2.9 ms
64 bytes from 192.168.100.50: icmp_seq=3 ttl=64 time=2.7 ms

--- dtivo ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.7/3.2/4.5 ms
root@tivo [199] #

root@tivo [201] # grep -i broadcast /var/log/tvlog
Oct 6 16:26:00 (none) KnownHost[250]: Added TiVoConnect broadcast address 192.168.100.255

[7.1]

...
upgrade 7.1 to 7.2 everything works fine with the network (e.g telnet, bash,
ftp etc.). However, the Tivo's don't see each other so there's no MRV.
...Which one of the approaches outlined in this (http://www.dealdatabase.com/forum/showthread.php?p=222641#post222641) post did you follow for configuring the 6.2 network? You might try the /sbin/hotplug command listed there to see if it starts the broadcasts up on the 6.2 machine.

[fgoodman]

I will try the hotplug, but I was using DHCP to setup the address.

I don't get why upgrading my SAS2 would cause my DTiVo to suddenly stop setting up a proper broadcast address?

I'll let you know if that helps...

F.

[eastwind]

I'm guessing at some point you did set_mrv_name?

ew

[fgoodman]

Bingo!

netconfig.tcl on the 6.2 box followed by the /sbin/hotplug did the trick.

Tivo's are a talking, shows are a tranferring, and a partridge in a pear tree !

Thanks for the pointer!

Now if somone would be so kind, I hate not understanding this.

So prior to upgrading my SAS2 from 7.1 to 7.2 my 6.2 DTiVo was
happily MRV'ing with with the SAS2.

If I understand things, by running netconfig.tcl, I added my static IP information to the MFS network database which allowed /sbin/hotplug to "force" the broadcast address setup on my 6.2 box.

Since absolutely nothing changed on my 6.2 box, how was I able to MRV with the SAS2 when it was running 7.1? Did something change in 7.2 (or
superpatch 1.1) that make MRV require this broadcast address where previously it did not? That's the only thing I can think of, but since TiVo
must have many customers still running old software this seems unlikely,
not by any means unheard of, but still unlikely...

Confusion seems to be a constant state of mind for me these days...

Thanks again for helping me straigten out the functional issues even if
I don't get why it worked :-)

Frank.

[barney34]

Can anyone tell me why test.conf no longer runs after slice upgrade to 6.2.

When I telnet to tivo my path does not include /busybox which was set in test.conf and when I look at the kernel logs it says ftpd and fakecall.tcl can not be found from rc.sysinit.author

[eastwind]

Can anyone tell me why test.conf no longer runs after slice upgrade to 6.2.

When I telnet to tivo my path does not include /busybox which was set in test.conf and when I look at the kernel logs it says ftpd and fakecall.tcl can not be found from rc.sysinit.author
Did you move test.conf to the new root?

ew

[barney34]

Did you move test.conf to the new root?

ew


Yep it is under / but I did not move it. It was there after the upgrade.

Under /dev/hda4 and the permissions are correct I guess (-rwxr-xr-x )

[eastwind]

Yep it is under / but I did not move it. It was there after the upgrade.

Under /dev/hda4 and the permissions are correct I guess (-rwxr-xr-x )
You should look at it. If you don't understand why, you need to do some reading. '/' is mounted in a different place on the hard drive after the upgrade completes.

ew

[NutKase]

Can anyone tell me why test.conf no longer runs after slice upgrade to 6.2.

When I telnet to tivo my path does not include /busybox which was set in test.conf and when I look at the kernel logs it says ftpd and fakecall.tcl can not be found from rc.sysinit.author

WHY is this here? Why is it being answered here?

EDIT - No Problem.


NutKase

[eastwind]

WHY is this here? Why is it being answered here?


NutKase
Good question. I apologize. I don't pay much attention to which thread a question gets asked in and I guess I should.

ew

[barney34]

Good question. I apologize. I don't pay much attention to which thread a question gets asked in and I guess I should.

ew


Sorry I realized this was the wrong thread and was going to put it in the right one but then I figured I would get my hand slapped for double posting. Thanks

[Nuke2000]

I get this error evertime i run superpatch

bash-2.02# ./superpatch-67all-NutKase-1.1.tcl
InitializeProgramOrDie (tivosh) failed: 0x10009
bash-2.02#


I have a 6.2 dtiov

[Jamie]

I get this error evertime i run superpatch

bash-2.02# ./superpatch-67all-NutKase-1.1.tcl
InitializeProgramOrDie (tivosh) failed: 0x10009
http://www.dealdatabase.com/forum/showthread.php?t=44307&highlight=failed%3A+0x10009

BTW, I found this pretty quickly with a search on the strings in your error message. You might see "Hints foir getting better search results". Look for (S1) here (http://www.dealdatabase.com/forum/showthread.php?t=37756).

[Barefooter]

:) Just wanted to comment that 7.1's post that suggested using ADH's suggestion of "ACTION=register INTERFACE=eth0 /sbin/hotplug net" to get
the 6.2 DTIVOs to see each other does work. My network is set up in the rc.sysint.author so as it was as documented here many times, to far into to boot cycle to catch it. Once I tried Option 4 from this thread on page 2 it solved all my problems. Thanks to 7.1 and ADH for the help.

[shutterfriend]

Does the current Superpatch-67all work still on TiVo version 7.2.1?

Thanks.

[7.1]

Here's the patch to the superpatch to add support for 7.2.1-oth. Lightly tested.

Porting to -tak- and -elm- should be similar, but I'm not motivated by the need myself. Perhaps someone with Humax and/or Pioneer hardware will take it on this time.

[mlemmo]

Hi,

I have 2 issues after running superpatch...

SD-DVR80 -- 1x300 GB. 4.01b with MRV/network working, superpatch-4all-NutKase-0.7.1, LBA-48

1. Browsing a tivo server from the DTivo - was viewing some photos, ok looked fine did some more browsing of folders on the PC from the DTivo, and it just rebooted, rebooted ok - system seems fine, not sure why it would crash while browsing...

2. Locks and limits, I have searched the threads with no luck, my issue is I can apply locks/limits to lock challels etc, and unlock a program BUT.. .when I go to relock (turn locks back on) the menu selection for "turn Parental limits on.." does not function, I have to go into ratings or some other menu like channel locks change a limit or lock and then it asks to actually set the password.

The main lock menu acts like you have locks/limits in effect (unlocked state) but will not let you turn it back on and the 4 hour relock also fails to relock, when I unlock a program it seems to actually remove the locks completely but the tivo menu does not know it.

Thanks for any help in advance.

[6numbers]

I applied the Superpatch to two DTiVos and according to the messages, everything went fine. I can see the other TiVo at the bottom of the Now Playing List but when I try to select it I get a message saying that programs cannot be transferred because the DVR is not enabled for transfers.

The only similar message I've seen in this thread was from someone who hadn't patched all his TiVos but both of mine are patched so why can't they transfer programs?

I was surprised to see that one machine had a number instead of the name I set. The telnet session log shows that the name was successfully set. When I tried to redo it though, I got the following error message:

Logger not initialized! Logging to stdout:
/etc/TvFeatures>Nov 14 00:11:34 TmkInit[275]: Can't read feature file:
InitializeProgramOrDie (tivosh) failed: 0x10009

The same thing happened when I tried to reapply the superpatch. Where do I go from here?

[jasch]

I presume after the superpatch, you ran set_mrv_name ?

[Gunnyman]

probably the certificate deal. Has your hacked DTivo ever called in?

[jasch]

Here's the patch to the superpatch to add support for 7.2.1-oth. Lightly tested.

Did you test MRV? I was able to pull programs from my 6.2 units to my 7.2.1-oth units, but not the other way around....

I keep getting "Sorry, you ca'nt watch this program now, either because the XXX Tivo DVR is no longer available on the network or because the requested program could no longer be found"

"Before trying again, make sure the XXX Tivo DVR is turned on, connected to the network, has the correct network settings, and stillc ontains the program you want to watch".

I ended moving up the programs using mfs_ftp between the tivos...

[7.1]

Did you test MRV? I was able to pull programs from my 6.2 units to my 7.2.1-oth units, but not the other way around....I tested between 7.x machines that had valid group certs, and with tivoserver. The one thing that didn't get tested is a client that's not in the group cert pulling from a 7.2.1 superpatched tivo. Sounds like that's the case that's causing you grief. I'm guessing I missed a patch in the port, but it's one that doesn't affect me, since all my tivo's are in the group cert, so I didn't notice.

Care to contribute to a solution? Did it used to work with 7.2.0-oth? If so, compare the 7.2.0-oth patch list against 7.2.1-oth. Does it look like there is a missing patch? Also, if there are any error messages in /var/log/tverr on the 7.2.1-oth box when the transfer fails, they might prove useful.

[jasch]

With 7.2.0-oth worked perfectly. I tried comparing both lists, but they obviously are different (different path address, different hex values for some).

My tverr says this:
TvNvSenderSession.C[329]: Couldn't get a secure key for client 3210001302DDEA0 - 0x1f0006

[6numbers]

I presume after the superpatch, you ran set_mrv_name ?Yes I did:
bash-2.02# set_mrv_name_67.tcl FamilyRoom
Setting nametable for "FamilyRoom"...
Reboot your tivo for the changes to take effect.
bash-2.02# reboot I tried set_mrv_name again when I couldn't transfer and got:
bash-2.02# set_mrv_name_67.tcl FamilyRoom
Logger not initialized! Logging to stdout:
/etc/TvFeatures>Nov 13 23:44:34 TmkInit[293]: Can't read feature file:
InitializeProgramOrDie (tivosh) failed: 0x10009