superpatch-67all - (Support)

[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"
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, 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?